stestr 4.1.0

This stestr release is a feature release that primarily fixes compatibility with subunit 1.4.3 and initial compatibility with Python 3.12.

Features

• Add support for configuring stestr via a pyproject.toml file.

What's Changed

• Apply black autoformatter to code base by @jogo in #332
• Reuse subunit_trace output/validation logic for load/run by @jogo in #333
• Revert "Fix #330 - Preserve load-list order" by @mtreinish in #335
• Remove vestigial future package from requirements by @0xDEC0DE in #338
• Pin black to 2022 version by @mtreinish in #343
• Fix ResourceWarning from SubunitTestRunner._list() by @mtreinish in #342
• Add support for storing stestr configs in pyproject.toml by @0xDEC0DE in #341
• Adding another prefix to the existing list of unittest_import_strs by @psathyan in #339
• Update docs job to avoid setup.py entrypoint by @mtreinish in #346
• Replace removed SafeConfigParser with ConfigParser by @hroncok in #344
• Explicitly list extras as dependency by @pshchelo in #348

New Contributors

• @jogo made their first contribution in #332
• @0xDEC0DE made their first contribution in #338
• @psathyan made their first contribution in #339
• @hroncok made their first contribution in #344
• @pshchelo made their first contribution in #348

Full Changelog: 4.0.0...4.1.0

stestr 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.

stestr 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 parity 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
  inadvertently broken at some point so that the execution order of
  the tests were shuffled

stestr 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.

stestr 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.