-
4.0.16e8997f5 · ·
Release 4.0.1 This stestr release is a bugfix release that fixes two issues that were identified in the 4.0.0 release. Fixes ----- * Fixed an issue around the unittest runner unexpectedly not running the requested tests (or executing them in an unexpected order) causing odd failures that were difficult to debug. * Fixed the output handling of `stestr run` and `stestr load` so that any segfaults or unexpected failures in a test worker are now properly reported in the subunit-trace output.
-
4.0.06edb3ed6 · ·
Release 4.0.0 This is a major version release because it drops support for the `'sql'` repository type and also the flags and Python API flags for selecting the repository type, which was deprecated in the 3.2.0 release. This was always an experimental feature that never reached feature pairity with the default ``'file'`` repository type. If you were relying on this repository type you should transition to using a file repository type and manually leverage subunit2sql to store data in a SQL database. This release also support for running with Python 3.5. If you're relying on being able to use stestr with Python 3.5 you can continue to use stestr < 4.0.0. New Features ------------ * Official support for Python 3.10. While 3.10 worked fine in previous stestr releases, this release is the first to include testing and mark support in the package metadata. Fixes ----- * Fixed the execution order of the stestr run --load-list option so that tests are executed in the order specified in the list. This was inadvertedtly broken at some point so that the
-
3.2.128892333 · ·
Release 3.2.1 This is a patch version release that contains a bugfix for the detection and reporting of instances where a test worker exits without reporting a test's final status. This is critical for debugging situations where there is a segfault or other system error in a test. Fixes ----- - Fixed the detection of test worker failures before reporting final result status (resulting in a test showing a status of "inprogress"). This enables reporting any tests that were running when the test worker exited.
-
3.2.07d655e4f · ·
Release 3.2.0 This is a minor version release that adds a couple new features and fixes bugs. New Features ------------ * Support for configuring stestr via a tox.ini file has been added. It's now no longer needed to create a separate .stestr.conf file and instead it can be embedded in an existing tox.ini file. * A new stestr command, `stestr history list` has been added to list the previous runs in the stestr repository. * A new stestr command, `stestr history show` has been added to show the output from a previous run from the stestr repository. * A new stestr command, `stestr history remove`, has been added to remove runs from the stestr repository. Deprecations ------------ * The 'sql' repository type has been deprecated and will be removed in the 4.0.0 release. This was never the default repository type and for its entire existence it was listed as an experimental feature. If you were relying on this repository type you should transition to using a file repository type and manually leverage subunit2sql to store data in a SQL database. * The `--repo-type`/`-r` common argument for switching the repository type has been deprecated and will be removed in the 4.0.0 release. Fixes ----- * Runs that have a worker crash outside of Python (typically with an error like a segfault) are now properly highlighted in the default subunit-trace output. Previously they would just silently be listed as 'inprogress' and not show as failed anywhere.
-
3.1.02e992517 · ·
Release 3.1.0 This is minor version release contains two major changes. The first is that this release is the first to officially support Python 3.9. While stestr ran fine with 3.9 before this, it wasn't tested or marked as supported in the package metadata previously. The other change made is that non-inclusive terminology which was previously used in the CLI has been deprecated and will be removed in a future release. New Features ------------ * Python 3.9 is officially a supported * Three new options, --include-list, --exclude-list, and --exclude-regex have been added to the run and list commands. These options are replacements for the previous non-inclusive terms used on these commands. Deprecations ------------ * The --whitelist-file, --blacklist-file, and --black-regex CLI arguments from all commands where they were used and the matching Python API parameters have been deprecated. They have been superseded by --include-list, --exclude-list, and --exclude-regex respectively.