cargo-nextest: baixar versions anteriors

Changed
- For setup scripts, slow-timeout no longer accepts on-timeout = "pass", and nextest now reports a configuration error if it is specified. A setup script that times out always fails the run. Previously, this setting was accepted but handled inconsistently: the timed-out script was counted as a failure, but the run was not cancelled. (#3640)
- Internal dependency updates: guppy updated to 0.19.1, and target-spec updated to 3.7.0, updating built-in targets to Rust 1.98.
Fixed
- Stress runs now exit with a non-zero code if any iteration failed. Previously, with fail-fast disabled, the exit code reflected only the last iteration, so a stress run with failures in earlier iterations exited with code 0 if the last iteration passed. (#3624)
- Stress runs now always run at least one iteration. Previously, --stress-duration with a very short duration (such as 1ns) could finish without running any tests. (#3633)
- Runs stopped by immediate fail-fast (--max-fail N:immediate) are now treated as failed rather than cancelled. Previously, in stress runs, the summary read 0 passed; cancelled due to test failure and the failing iteration was not counted as failed. (#3639)
- When the global timeout fires with immediate fail-fast enabled, nextest now reports the global timeout as the reason the run was cancelled. Previously, the tests terminated by the timeout counted as failures, so nextest printed a second Cancelling due to test failure line and reported a test failure as the reason. (#3637)
- After the global timeout fires, nextest no longer keeps a CPU core busy while it waits for running tests to shut down. (#3647)
- The leak timeout is no longer restarted each time a leaked handle produces output, or each time nextest handles a signal or an info request while waiting. Previously, a test that exited while leaving behind a process that kept writing to standard output or standard error could delay leak detection indefinitely. (#3646)
- If waiting on a test or setup script process fails, nextest now reports the test or script as an execution failure, with the underlying error shown. Previously, nextest panicked. (#3643)
- The Cancelling and Killing status lines no longer contain stray colons. Previously, nextest printed lines like Killing due to second signal: : 1 test still running, and a trailing colon when nothing was still running. (#3641)
Internal improvements
- Source builds of nextest no longer compile two versions of zstd. (#3620)
Thanks Jake-Shadle for your contribution!

Fixed
- Updated chacha20 and der to non-yanked versions.

Changed
- Configuration diagnostics now name the file each setting came from. For example, cargo nextest show-config version shows which file specified the nextest-version requirement, and cargo nextest show-config test-groups shows which file each override was defined in.
For now, this is most useful when tool-specific config files are in play, but upcoming work to support local configuration files also benefits from this. (#3580, #3584)
- Config file paths in errors and warnings are now displayed relative to the directory nextest is invoked from, following typical CLI conventions. Previously, parse errors showed absolute paths and warnings showed paths relative to the workspace root. In stylized output, config file paths are now colored as well. (#3568, #3570, #3577)
Fixed
- Per-test overrides and setup and wrapper scripts defined in a profile's inheritance chain are now applied. Previously, only the selected profile's own overrides and those in profile.default were consulted, so overrides in intermediate profiles were silently skipped. As part of this change, a profile that does not set default-filter now inherits it from the nearest ancestor that does, rather than always from profile.default. (#3585)
- A default-filter set by a tool config file is now respected when the repository config does not set one. Previously, the tool's filter was ignored and all() was used. (#3592)
- Profile inheritance cycles that span multiple config files, such as a tool config file redefining a profile that the repository config inherits from, are now detected and reported as errors. Previously, cycles were only detected within a single file. (#3588)
- Passing --tool-config-file more than once for the same tool name now produces an error. Previously, nextest panicked internally. (#3589)
- The hint shown when a command requires an experimental feature that isn't enabled now points at the correct config file path when nextest is run from a subdirectory of the workspace, from outside the workspace, or with an explicit --config-file. (#3565)
- On Unix platforms where the Rust standard library cannot create pipes with FD_CLOEXEC set atomically (most notably Apple platforms), a test could inherit a sibling test's capture pipe if the two were spawned concurrently. The sibling was then reported as having leaked handles after it exited. Nextest now creates capture pipes itself and coordinates pipe creation with process spawning, so that spawns no longer inherit stray pipes. (#3553)
An upcoming design document will go over how nextest spawns processes in detail, including more information about this workaround.
Thanks gaborbernat for your first contribution!

Changed
- Failures while setting up run recording (for example, a store directory that cannot be created) are now always reported as warnings, and the test run continues without recording. Previously, only a store format version mismatch was treated as a warning, and other setup failures aborted the run. This makes setup consistent with recording finalization, which already never fails a run. (#3547)
- The "continue rerunning" hint printed when a rerun has outstanding tests is now only shown when the rerun was itself recorded, since cargo nextest run -R latest can only continue the chain in that case. (#3548)
Fixed
- Fixed the elapsed time shown in per-test running lines for tests that had been running for more than an hour. The minutes field was displayed as the total number of minutes rather than the minutes within the hour, producing output like [05:313:30]. (#3535)
- When a cargo metadata or cargo build invocation fails, the error message now shows the full list of arguments that were passed to Cargo, including --color and --manifest-path. Previously, some arguments were omitted from the message. (#3557)
Thanks chirizxc, latent-9, and k-cross for your first contributions!

Added
- A new junit.report-skipped configuration setting controls which skipped tests are emitted in the JUnit XML report as <testcase> elements with a <skipped> child. (#885)
Thanks to liangfu for your first contribution!
- While listing tests, nextest now shows a progress bar if listing takes longer than 2 seconds. Listing is usually fast, but can be slow in some environments, such as with antivirus software that scans each test binary before it runs. (#3471)
- The binaries metadata (used by archives and --binaries-metadata) now records whether Cargo built each non-test binary for the host or the target platform. Future versions of nextest will use this to configure environment variables correctly in cross-compilation scenarios. (#3520)
Changed
- Nextest now orders the dynamic library search path the way current versions of Cargo do, with the Cargo artifact directory ahead of the deps directory. Previously the two were reversed, so a test could potentially resolve a dylib to a different copy than cargo test would. (Cargo swapped the two in 1.93.)
Fixed
- Nextest now computes the dynamic library search path correctly under build directory layout v2, which became the default on nightly Rust on 2026-07-30. Previously, tests that linked against a dylib dependency failed to start because the dynamic library could not be found.
- When Cargo's build.build-dir is configured, nextest now adds the Cargo artifact directory (where final artifacts like binaries and dynamic libraries are uplifted to) instead of the build directory (for intermediate artifacts) to the dynamic library search path. This matches Cargo's behavior.
- Nextest now detects the base output directory for test binaries built from [[example]] targets, which Cargo places in examples rather than deps. Previously, a run restricted to examples didn't add anything to the dynamic library search path, so an example test linking against a dylib failed to start.
- While creating an archive with a filterset, nextest now always includes dynamic libraries in the archive, even those from packages whose test binaries are all filtered out. Dynamic libraries are on the library search path and may be loaded by tests in other packages. Binaries exposed via CARGO_BIN_EXE_<name> are still filtered out if no test binaries from that package are selected. (#3516)
- The "Archiving" message now counts non-test binaries correctly. Previously, nextest counted the number of packages containing non-test binaries rather than the number of binaries. (#3515)

Added
- A new cargo nextest help <topic> subcommand renders reference documentation directly in the terminal. The available topics are:
- filterset (alias filtersets): the filterset DSL reference
- repo-config: the repository configuration reference
- user-config: the user configuration reference
cargo nextest help lists the available topics. (#3419, #3424, #3432, #3433)
Changed
- The glibc requirement for pre-built aarch64-unknown-linux-gnu and riscv64-unknown-linux-gnu builds has been lowered to glibc 2.27.
- riscv64-unknown-linux-gnu now uses rustls + aws-lc-rs rather than OpenSSL.

Added
- Nextest now sets the following environment variables during the list phase, not just the run phase:
- NEXTEST_VERSION
- NEXTEST_REQUIRED_VERSION
- NEXTEST_RECOMMENDED_VERSION
- NEXTEST_RUN_ID
- NEXTEST_BINARY_ID
- NEXTEST_WORKSPACE_ROOT
This lets target runners and custom test harnesses use this information while listing tests. (#3410)
Changed
- When --cargo-metadata is passed without --binaries-metadata, and the Cargo metadata contains exactly one default member (for example, metadata generated with --manifest-path path/to/package/Cargo.toml), nextest now anchors the build scope to that member's Cargo.toml rather than widening it to the entire workspace. (#3409)
- --workspace-remap now requires both --cargo-metadata and --binaries-metadata. The combination of --workspace-remap and --cargo-metadata cannot work without --binaries-metadata, so nextest now reports this as an error up front. (#3409)

Changed
- CLI --help descriptions, configuration-reference docs, and JSON schema descriptions now use consistent language and voice. (#3366)
Fixed
- Filterset expressions like not(test(foo)), all()and(test(foo)), and all()or(test(foo)), where not, and, or or is immediately followed by an opening parenthesis, now parse correctly. Previously, a separating space was required. (#3367)

Added
- Following up from the recently-added schema for repository configuration, nextest now also provides a JSON Schema for user configuration. The schema for the running version can be obtained by running cargo nextest self schema user-config. (#3351)
Changed
- The max-progress-running user-config setting no longer accepts numeric strings like "8" (an undocumented fallback). The supported values remain a non-negative integer (e.g. 8) or "infinite". (#3350)

Fixed an issue with a from-crates.io build.

Added
- Nextest now supports a group() filterset predicate for CLI filter expressions, allowing tests to be listed or run by their assigned test group. (#3273)
For example, to run all tests in a specific group:
cargo nextest run -E 'group(my-group)'
To list all tests that aren't in the default global group:
cargo nextest list -E 'not group(@global)'
- As part of cargo test binary emulation, --nocapture can now be passed in after --.
Fixed
- When --status-level fail is set, slow test notifications were previously displayed in a corrupt format (the duration and test name were shown, but the status was omitted). Slow notifications are now correctly hidden. (#3236)
- On Windows, pressing t for test status info no longer shows the output twice; nextest now only reacts to key-press events, ignoring key-release events. (#3225)
Security
- Update rand to 0.10.1 for RUSTSEC-2026-0097 / GHSA-cq8v-f236-94qc. Note that based on the advisory description, this unsoundness does not appear to affect nextest, since none of the covered rand versions have the log feature turned on.
- Update rustls-webpki to 0.103.10.

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

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)

Added
- Nextest now sets several new environment variables for tests and setup scripts: (#3103)
- NEXTEST_VERSION: the current nextest version as a semver string.
- NEXTEST_REQUIRED_VERSION and NEXTEST_RECOMMENDED_VERSION: the minimum required and recommended nextest versions from the repository's nextest-version configuration. If not configured, the value is "none".
- NEXTEST_TEST_THREADS: the computed number of test threads for this run.
- NEXTEST_WORKSPACE_ROOT: the absolute path to the workspace root (respects --workspace-remap).
- Nextest now sets CARGO_BIN_EXE_<name> at runtime for integration tests and benchmarks, matching cargo test in Rust 1.94 and above. Nextest sets this variable on all Rust versions. (#3137)
Previously, nextest only set NEXTEST_BIN_EXE_<name>, which remains available (and, with underscores, continues to be the recommended form). The CARGO_BIN_EXE_<name> form improves compatibility with tests written for cargo test.
Changed
- The automatic migration of recorded test runs from the cache directory to the state directory, introduced in version 0.9.126, has been removed. Records in the old cache directory location will no longer be migrated. (#3101)
Fixed
A couple of displayer fixes:
- Better sorting for the final summary when counters aren't displayed. (#3100)
- Fixed counter width padding in progress output to use the run count rather than the total test count. (#3102)
Internal improvements
- Cargo JSON output is now streamed directly into the binary list, making binary listing around 6% faster on large workspaces. (#3131) Thanks cornmander for your first contribution!

Changed
- --show-progress=only now behaves like the default auto in non-interactive mode, showing successful tests with a counter. This change was made because only is primarily intended for interactive scenarios. (#3087)
- The MSRV for building nextest has been updated to Rust 1.91.
Fixed
- Setup scripts that write NEXTEST-prefixed environment variables to $NEXTEST_ENV now properly report failure. Previously, the setup script would be reported as successful despite invalid variables, and tests would still run. (#3094)
Internal improvements
- Replay output is now only loaded from the archive when needed. This makes replays around 10-15% faster. (#3090)
- Switched from the zip crate to eazip to address repeated semver breakage in the zip crate. (#3093)

Fixed
Updated the zip crate to 8.0.0 since versions 7.3.0 and 7.4.0 were yanked.

Fixed
- In custom target JSONs, panic-strategy = "immediate-abort" now parses correctly (#2922).

Added
- Support for using a pager like less with nextest's output. Currently supported are:
- cargo nextest list
- cargo nextest show-config test-groups
- -h and --help commands
The pager support is closely modeled after the Jujutsu version control system. The default pager is less -FRX on Unix platforms, and a builtin pager (based on sapling-streampager) on Windows.
- cargo nextest self update now supports --beta and --rc flags to update to prerelease versions.

Added
- Nextest profiles now support inheritance via the inherits key. For example:
[profile.ci]
retries = 2
[profile.ci-extended]
inherits = "ci"
slow-timeout = "120s"
Thanks asder8215 for your first contribution! (#2786)
- A new on-timeout option for slow-timeout allows tests that time out to be treated as successes instead of failures. This is useful for fuzz tests, or other tests where a timeout indicates no failing input was found. For example:
[[profile.default.overrides]]
filter = 'package(fuzz-targets)'
slow-timeout = { period = "30s", terminate-after = 1, on-timeout = "pass" }
Tests that time out and pass are marked TMPASS. See Configuring timeout behavior for more information.
Thanks eduardorittner for your first contribution! (#2742)
Changed
- MSRV updated to Rust 1.89.

Added
- A new config option --tracer enables running a test under a system call tracer like strace or truss. This mode is similar to --debugger added in version 0.9.113, but is optimized for non-interactive sessions. See this table for a comparison of behaviors.

Added
- Nextest now supports running tests under a debugger. Use --debugger to run a single test under gdb, lldb, WinDbg, CodeLLDB in Visual Studio Code, and other debuggers, while preserving all the environment setup done by nextest.
Nextest's debugger support will likely see some iteration and improvements over time. If it's missing a feature, please open a feature request, or even better, send a pull request!
- Nextest now sets NEXTEST_BIN_EXE_* environment variables with hyphens in binary names replaced by underscores, in addition to the existing variables with hyphens. This works around some shells and debuggers that drop environment variables containing hyphens. (#2777)
Fixed
- Fixed a panic when attempting to display progress during retries. (#2771)
- With stress tests, the progress bar no longer overwrites unrelated output. (#2765)
- During the list phase, invalid output lines with control characters in them are now properly escaped. (#2772)
Other
- Nextest's GitHub releases are now marked immutable, so for a particular version, its release binaries can't be changed by anybody after publication. (Release binaries have never changed as a matter of policy. The improvement here is that for 0.9.113 and future versions, this fact is now cryptographically attested by GitHub.)

Added
- Nextest now supports immediately terminating currently-running tests on failure. Set fail-fast = { max-fail = 1, terminate = "immediate" } in your configuration, or use --max-fail=1:immediate, to terminate running tests as soon as the first test fails.
Changed
- In interactive terminals, nextest now shows 8 running tests by default underneath the progress bar. Control the maximum number of tests displayed with the --max-progress-running option.
As part of this change, --show-progress=running is now an alias for --show-progress=bar. To only show running tests, use --show-progress=only.
- Non-UTF-8 test output is now encoded with String::from_utf8_lossy before being printed out to the terminal. This should generally not be a visible change, since most tests produce UTF-8 output.
- When the progress bar is displayed, nextest now writes to terminal output every 50ms.
Fixed
- A number of performance improvements to running test output. Thanks glehmann for your work on polishing this feature!

Added
- OSC 9;4 in-terminal progress bars are automatically enabled when the Ghostty terminal is detected. Thanks adamchalmers and RGBCube for your first contribution!
Fixed
- With --show-progress=running, the global progress bar now stays in place more often, providing a smoother visual experience.
Changed
- MSRV for building nextest updated to Rust 1.88.
Internal improvements
- USDT probes now include additional context: global_slot, group_slot, and test_group fields for test attempt events.
- Miscellaneous performance improvements to --show-progress=running and only.

Added
- A new running progress mode that shows currently running tests in addition to the progress bar. Use --show-progress=running to see both running tests and information about successful tests, or --show-progress=only for a more compact output showing only running tests, without displaying any output related to successful tests.
Thanks glehmann for your first contribution!
- The cargo nextest archive command now supports binary filtering via the --filterset or -E options. This allows you to reduce the size of archives by including only a subset of test binaries. Note that test binaries are not executed during archiving, so test() predicates are not supported.
Thanks clundin55 for your first contribution!
Fixed
- Improvements to --show-progress=counter for better output formatting and reliability.
Other improvements
- USDT probes now include additional events:
- Updated run-start and run-done events to include stress run information.
- New stress-sub-run-start and stress-sub-run-done events for tracking individual stress run iterations.
- Test completion events now include stdout_len and stderr_len fields for output size tracking.

Added
- Support for USDT (User-level Statically Defined Tracing) probes for observability and debugging. USDT probes allow tools like DTrace and bpftrace to trace nextest's internal operations. The initial probes cover test execution lifecycle events.
For more information, see the USDT documentation.
- In CI, test status lines now include a counter showing the number of tests that have been executed (#2618). Thanks bobrik for your first contribution!
Changed
- For leaky tests, default leak timeout increased from 100ms to 200ms.
- MSRV for building nextest updated to Rust 1.87.

Fixed
- For custom targets, updated the deserializer to handle target-pointer-width becoming an integer in the newest Rust nightlies.
Changed
- Update builtin list of targets to Rust 1.90.

Changed
On Windows, job objects are now created with JOB_OBJECT_LIMIT_BREAKAWAY_OK. This enables test processes to have their children be assigned a different job object, which is particularly relevant on Windows 7 since that platform doesn't have nested job objects.
Thanks to Guiguiprim for the contribution!

Added
- For stress tests, summary lines now indicate the number of iterations passed and/or failed.
Changed
- Always forward --config arguments to Cargo invocations. Thanks to benschulz for your first contribution!
- Internal dependency update: target-spec updated to 3.5.1, updating built-in targets to Rust 1.89.

Added
- Initial support for stress tests: running tests a large number of times in a loop.
Changed
- The libtest-json-plus output now produces test results immediately rather than at the end of the run. This is allowed by the fact that with the libtest-json-plus output, it is possible to distinguish between different test binaries based on the additional nextest property.
Thanks to dnbln for your first contribution!
Fixed
- The heuristic detection for panicked at in tests now handles the new output format in Rust nightlies (Rust 1.91 and above): on Unix platforms, the thread ID is now also included.
Thanks again to dnbln for fixing this.