100.0 The 100¶
The Avocado team is proud to present another release: Avocado 100.0, AKA “The 100”, is now available!
Release documentation: Avocado 100.0
- Asset cache checksum can now use multiple hash algorithms. The
ability to store multiple hashes, created by different algorithm to
CHECKSUMfile was added. This is useful when different tests refer to the same asset, but use different hash algorithms.
- Information on a test’s file name was introduced in the xunit/junit result files. Although not a standard field everywhere, this information is used and displayed on platforms such as GitLab.
- Python 3.11 (final) is now formally supported and tested on CI.
core.input_encodingwere settings were removed, and now default to the the system’s setting (by using
- Command line options prefixed with
--nrunner-had that prefixed removed. A command line option such as
--nrunner-spawneris now simply
--spawner. The matching configuration options such as
run.something. This is due to the fact that nrunner is now the only runner implementation offered by default, so the differentiation and extra typing seems unnecessary. If other runners are added in the future (or by custom, out of tree, plugins) they can choose to respect the existing options if they apply.
avocado jobs get-output-filescommand was removed. Its original intended purpose has not been relevant for some time, and the preservation of output files are already handled directly by all spawner implementations.
- Fixed a limit for
taptests, where the
STDERRbuffers could be exhausted, and the test would get stuck forever on further writes. The
taprunners can now make use of the (optional)
output_dirparameter, resulting in a much more efficient I/O handling. When
output_diris used, the only limitation on
STDERRis the file-system itself.
--showoption was not being respected when running
avocado-instrumentedtests. The log messages generated by, say, an
avocado.test.foologger, should be presented at the Avocado job UI as it happens, provided
- An existing aid for the usage of Avocado running from Python eggs
would result in unnecessary changes to the
PYTHONPATH. Those changes could cause unpredictable Python module import behavior.
- Fixed a condition in which, when failing to import Python modules on
tests, the error message returned was
Test.__init__() got an unexpected keyword argument 'run.results_dir'which was quite cryptic and confused users.
- The assets fetch plugin won’t attempt to fetch and cache the assets of the same test more than once.
- Running tests’ statuses are now properly marked as
CANCELwhen they reach their own (or the job) timeout.
avocado jobs showcommand used to show a simplified and possibly incorrect information about the spawner used. This information is no longer displayed, given that it’s a test suite attribute, and not really a job level information.
- The Podman spawner could fail to preserve the output directory when users on the host and the container did not match. This has now been fixed.
- The resolver received the same kind of test coverage as the legacy loader architecture, in preparation for the removal of the loader.
- The Fedora version used on selftests related to the Podman spawner
were pinned to 36. The reason is that, because of the release of
Fedora 37, which has Python 3.11, no
setuptoolsor Avocado eggs are available for Python 3.11 yet.
- Removal of the generic
avocado-runnerrunner, which is a reminiscent of the all-in-one
nrunner.pyfile, for ease of deployment. With the nrunner split and now deployed via Python eggs, it does not have to exist anymore.
- Selftests will no longer not store temporary results in user’s default results directory.
For more information, please check out the complete Avocado changelog.