nextest-runner 0.113.0

nextest-runner-0.113.0

[nextest-runner] version 0.113.0

nextest-filtering 0.20.0

Changed

• winnow updated to 1.0.0.

cargo-nextest 0.9.132

Update aws-lc-sys to 0.39.0 to address GHSA-394x-vwmw-crm3.

cargo-nextest 0.9.132-rc.3

Update aws-lc-sys to 0.39.0 to address GHSA-394x-vwmw-crm3.

cargo-nextest 0.9.132-rc.1

Update aws-lc-sys to 0.39.0 to address GHSA-394x-vwmw-crm3.

nextest-runner 0.112.0

nextest-runner-0.112.0

[nextest-runner] version 0.112.0

cargo-nextest 0.9.131

Added

• Setup scripts and wrapper scripts can now specify per-command environment variables via the env field in the command configuration. (#3001)

  For example:

  [scripts.setup.script1]
  command = {
      command-line = "cargo run -p setup-test-db",
      env = {
          DB_PATH = "sqlite:/path/to/source.db",
      },
  }

  Keys cannot begin with NEXTEST, as that prefix is reserved for internal use. Values defined in env override values set by the environment and by Cargo's config.toml (including those with force = true).

  Thanks metatoaster for your first contribution!

• A new flaky-result configuration field and --flaky-result CLI flag (environment variable NEXTEST_FLAKY_RESULT) controls whether flaky tests are treated as passing or failing. When set to "fail", tests that pass on retry are marked as failures. The default remains "pass". flaky-result can be set at the profile level or per-test via overrides. (#3148)

  For more information, see Failing flaky tests.

  [profile.ci]
  retries = 2
  flaky-result = "fail"

• A new cargo nextest store export-chrome-trace command that exports test run data in the Chrome Trace Event format. Traces can be loaded into Perfetto or Chrome's chrome://tracing for a timeline view of test parallelism and execution. (#3163)

  cargo nextest store export-chrome-trace latest -o trace.json

  Traces support grouping by binary (default) or by slot (--group-by slot), and can be exported from both on-disk runs and portable recordings. For more, see Perfetto traces.

• Added release binaries for riscv64gc-unknown-linux-gnu. These binaries are cross-compiled from x86_64 Linux and are not currently tested.

Fixed

• Nextest now works with the new build directory layout (-Zbuild-dir-new-layout), and with the build directory being separate from the target directory (build.build-dir). (#3168, #3169)

Changed

• When retries are enabled, nextest no longer shows TRY 1 SLOW messages for the first attempt. TRY N SLOW is still shown for subsequent attempts.

Miscellaneous

• Self-update (cargo nextest self update) now uses ureq instead of reqwest and replaces the ring dependency with aws-lc-rs. This may require you to install CMake if you're on a less-commonly-used platform. (#3141)

Internal improvements

• Breaking change to the recording format: recordings now include test group and slot information, enabling Chrome trace export from recordings. (#3158)

nextest-metadata 0.14.0

Added

• A new build_directory field on RustBuildMetaSummary. When Cargo's build.build-dir is configured, the build directory (for intermediate artifacts) differs from the target directory. This is None when parsing metadata from older nextest versions, in which case consumers should treat it as equal to target_directory.
• A new build_script_info field on RustBuildMetaSummary, keyed by package ID. This is None when parsing metadata from older nextest versions.
  • The values of this map are BuildScriptInfoSummary structs, which currently contain an envs field consisting of environment variables set by cargo::rustc-env directives.

Changed

• base_output_directories, build_script_out_dirs, and linked_paths are now documented as relative to the build directory rather than the target directory.

nextest-filtering 0.19.0

Changed

• nextest-metadata updated to 0.14.0.
• MSRV updated to Rust 1.91.

nextest-runner 0.112.0-rc.3

nextest-runner-0.112.0-rc.3

[nextest-runner] version 0.112.0-rc.3