cargo-nextest 0.9.18

Added

Added

• Support for terminating tests if they take too long, via the configuration parameter slow-timeout.terminate-after. For example, to time out after 120 seconds:

  slow-timeout = { period = "60s", terminate-after = 2 }

  Thanks steveeJ for your contribution (#214)!

Fixed

• Improved support for reusing builds: produce better error messages if the workspace's source is missing.

nextest-runner 0.9.0

This release contains a number of user experience improvements.

Added

• If producing output to an interactive terminal, nextest now prints out its status as a progress bar. This makes it easy to see the status of a test run at a glance.
• Nextest's configuration has a new final-status-level option which can be used to print out some statuses at the end of a run (defaults to none). On the command line, this can be overridden with the --final-status-level argument or NEXTEST_FINAL_STATUS_LEVEL in the environment.
• If a target runner is in use, nextest now prints out its name and the environment variable or config file the definition was obtained from.

Changed

• If the creation of a test list fails, nextest now prints a more descriptive error message, and exits with the exit code 104 (TEST_LIST_CREATION_FAILED).

nextest-metadata 0.4.1

Added

• New documented exit code TEST_LIST_CREATION_FAILED.

cargo-nextest 0.9.17

This release contains a number of user experience improvements.

Added

• If producing output to an interactive terminal, nextest now prints out its status as a progress bar. This makes it easy to see the status of a test run at a glance.
• Nextest's configuration has a new final-status-level option which can be used to print out some statuses at the end of a run (defaults to none). On the command line, this can be overridden with the --final-status-level argument or NEXTEST_FINAL_STATUS_LEVEL in the environment.
• If a target runner is in use, nextest now prints out its name and the environment variable or config file the definition was obtained from.

Changed

• If the creation of a test list fails, nextest now prints a more descriptive error message, and exits with the exit code 104 (TEST_LIST_CREATION_FAILED).

nextest-runner 0.8.1

Added

• Nextest now sets NEXTEST_LD_* and NEXTEST_DYLD_* environment
  variables to work around
  macOS System Integrity Protection sanitization.

Fixed

• While archiving build artifacts, work around some libraries producing linked paths that don't exist (#247). Print a warning for those paths instead of failing.

Changed

• Build artifact archives no longer recurse into linked path subdirectories. This is not a behavioral change because LD_LIBRARY_PATH and other similar variables do not recurse into subdirectories either.

cargo-nextest 0.9.16

Added

• Nextest now sets NEXTEST_LD_* and NEXTEST_DYLD_* environment
  variables to work around
  macOS System Integrity Protection sanitization.

Fixed

• While archiving build artifacts, work around some libraries producing linked paths that don't exist (#247). Print a warning for those paths instead of failing.

Changed

• Build artifact archives no longer recurse into linked path subdirectories. This is not a behavioral change because LD_LIBRARY_PATH and other similar variables do not recurse into subdirectories either.

nextest-runner 0.8.0

Added

• Support for creating and running archives of test binaries.
  • Most of the new logic is within a new reuse_build module.
• Non-test binaries and dynamic libraries are now recorded in BinaryList.

Fixed

Fix for experimental feature filter expressions:

• Fix test filtering when expression filters are set but name-based filters aren't.

Changed

• MSRV bumped to Rust 1.59.

nextest-metadata 0.4.0

Added

• Support for archiving test binaries:
  • Non-test binaries and dynamic libraries are now recorded to RustBuildMetaSummary.

Changed

• Minimum supported nextest version bumped to 0.9.15.
• MSRV bumped to 1.59.

cargo-nextest 0.9.15

Added

• Improved support for reusing builds:
  • New command cargo nextest archive automatically archives test binaries and other relevant
    files after building tests. Currently the .tar.zst format is supported.
  • New option cargo nextest run --archive-file automatically extracts archives before running the tests within them.
  • New runtime environment variable NEXTEST_BIN_EXE_<name> is set to the absolute path to a binary target's executable, taking path remapping into account. This is equivalent to CARGO_BIN_EXE_<name>, except this is set at runtime.
  • cargo nextest list --list-type binaries-only now records information about non-test binaries as well.

Fixed

Fix for experimental feature filter expressions:

• Fix test filtering when expression filters are set but name-based filters aren't.

nextest-runner 0.7.0

Fixed

• PathMapper now canonicalizes the remapped workspace and target directories (and returns an error if that was unsuccessful).
• If the workspace directory is remapped, CARGO_MANIFEST_DIR in tests' runtime environment is set to the new directory.