cargo-nextest 0.9.89

Added

• To configure fail-fast behavior, max-fail can now be specified in configuration. For example, to fail after 5 tests:

  [profile.default]
  fail-fast = { max-fail = 5 }

  fail-fast = true is the same as { max-fail = 1 }, and fail-fast = false is { max-fail = "all" }.

  Thanks to Jayllyz for your first contribution!

• Within tests and scripts, the NEXTEST_PROFILE environment variable is now always set to the current configuration profile. Previously, this would only happen if the profile was configured via NEXTEST_PROFILE, as a side effect of the environment being passed through.

Changed

• The --max-fail and --no-tests options no longer require using an equals sign. For example, --max-fail 5 and --max-fail=5 now both work.

  This was previously done to avoid confusion between test name filters and arguments. But we believe the new --no-tests default to fail sufficiently mitigates this downside, and uniformity across options is valuable.

Fixed

• Nextest now uses rustc -vV to obtain the host target triple, rather than using the target the cargo-nextest binary was built for. This fixes behavior for runtime cross-compatible binaries, such as -linux-musl binaries running on -linux-gnu.
• If nextest is paused and later continued, the progress bar's time taken now excludes the amount of time nextest was paused for.
• Update rust-openssl for CVE-2025-24898.

Miscellaneous

• Nextest now documents the safety of altering the environment within tests. As a result of nextest's process-per-test model, it is generally safe to call std::env::set_var and remove_var at the beginning of tests.
• With Rust 1.84 and above, builds using musl no longer have slow process spawns. With this improvement, glibc and musl builds of nextest are now roughly at par, and should have similar performance characteristics.