Hi,
This 1.4 release fixes a bug when viewing all test results page and
enables more filtering options for build and testrun api endpoints.
Complete list of changes going in:
* api:
* rest: enable filtering testruns by 'completed'.
* rest: enable created date filtering on for builds in api
* frontend:
* tests: remove unnecessary ordering
* tests: reduce queries to list tests
* tests: simplify count of pages
* tests: remove duplicate queries to metadata
* tests: fix bug when listing tests without metadata
Cheers,
Charles
Hi,
This 1.3.1 release includes a minor bug in the api and support to work
with AWS SQS:
* settings:
* add support to custom polling interval
* add support to prefix-named queues
* turn on debug only when needed
* api: fix URL pattern for api/ paths
* http: authenticate users before checking permissions
* Add coverage testing with pytest
Hi,
This 1.3 release fixes a 500 http error code when accessing linux-log-parser
tests, also improving its log detection, including `WARNINGS`.
The release also fixes some minor issues related to docker setup, among
other new features and fixes that you can see in the full log below:
* core:
* test_history: handle tests with no metadata
* plugins: linux_log_parser: improve kernel log parsing
* frontend: reduce query time fetching metric names
* misc:
* debug: add django debug toolbar
* doc: add firewall note when running on docker
* Dockerfile: ignore version constraints from requirements.txt
Charles
Hi,
This 1.2 release fixes a couple of performance issues when fetching testjobs
from backends and when using the REST api, among other small fixes.
It stops ignoring duplicated tests for same environments and test suites
when calculating build summary (e.g. number of passing and failing tests).
Instead, use partial summaries already calculated for test runs.
We tweaked the backend code that fetches tests before calculating
regressions and fixes. If a build had a significant high number of test runs
it would make comparison much slower. So we avoid querying all test runs at
once when running `TestComparison`.
There were changes in the backend code of the REST api that reduced the number
of trips to db, making some endpoints load faster.
Complete changelog below:
# 1.2
* core:
* comparison: remove the use of iterator over tests
* comparison: filter tests by chunks of testruns
* comparison: fetch only id from testruns
* comparison: filter tests by testrun ids
* comparison: prefetch known issues
* comparison: lowered number of testruns chunk
* tasks: ReceiveTestRunData: ignore tests and metrics with long names
* models: remove duplicate call to build.finished
* test_summary: simplify summary calculation
* project: reduce amount of trips to database
* environment: set default expected_test_runs to zero
* build: make finished false when no jobs or testruns
* migrations: add missing migration for Django upgrade
* Group: sort aggregate query explicitly
* plugins: ignore most parameters
* ci:
* lava: handle unicode errors gracefully
* lava: fetch jobs right away
* listener: respect Backend listen_enabled
* Backend: add listen_enabled attribute
* doc:
* fix typo in .readthedocs.yml
* add configuration for readthedocs build
* api:
* disable post forms
* rest: reduce amount of queries and speed up some queries
* utils: remove duplicate DRF backend
* rest: avoid queries containing all projects
* rest: test: reduce number of queries in the database
* rest: remove deprecation warnings against django-filters 2.x
* Added translations:
* French
* misc:
* worker: don't constrain concurrency by default
* squad.urls: replace deprecated shortcut function
* tests: remove unecessary usage of Django's TestCase class
* core, ci: stop pytest from confusing our Test* classes with tests
* test_test: avoid pytest confusing helper method with a test
* pytest.ini: add pytest configuration
Hello,
squad 1.1 was just released. There are no large changes, but since there
was some internal reorganization it's being released as a minor update
and not a 1.0.x. Everything should just work when upgrading, though.
Most of the changes are targetting performance improvements in the
processing of background tasks.
Changelog:
* ci/lava: replace concatenation with StringIO
* settings: split tasks to separate queues
* requirements.txt: fix minimal version for pyyaml
* squad.run.worker: listen on all configured queues by default
* doc: document how to manage different queues
Hello,
We have just released squad 1.0.3. This release includes a fix for a
longstanding performance issue when fetching very large lava logs.
Full changelog:
# 1.0.3
* api: utils: add CursorPaginationWithPageSize
* Added translation using Weblate (French)
* ci/lava: adjust hangling of malformed logs yaml for newer PyYAML
* ci/lava: resubmit: exit early
* ci/lava: extract handling of failed submissions
* ci/lava: resubmit: handle errors on the LAVA side
* api: resubmit: handle submission errors gracefully
* ci: lava: speed up conversion of YAML of logs to pain text
Hi,
This release fixes a small issue with the gerrit plugin that
attempts to send notification with malformed patch_id.
Complete changelog below:
* plugins:
* plugins: gerrit: check patch_id before sending notification
* Updated translations:
* French (updated)
Hi,
This release includes bug fixes regarding yaml parsing. There was a
bug that saved test job definitions as bytes instead of strings,
messing up with that job completely.
Full changelog below:
* core:
* `yaml_validator`: drop usage of simple yaml.load
* api:
* api: ci: fix definition file encoding
* Updated translations:
* Polish (completed)
* French (added)
Charles
Hi all,
I have an issue which is certainly related to bad configuration.
I run xTS test job with LAVA to test Android images, so it makes a lot of
results for SQUAD to process and store (around 500k per build). My db
backups start to take some space, so I want to clean old results. But when
I try to delete a build, the connection is reset by SQUAD. I guess this is
due to worker timeout, so how can I fix this ?
Best regards,
Axel
