Update dependency cargo-nextest to v0.9.111

[renovate]

This PR contains the following updates:

Package	Update	Change
cargo-nextest	patch	0.9.103 -> 0.9.111

---

Release Notes

nextest-rs/nextest (cargo-nextest)

v0.9.111: cargo-nextest 0.9.111

Compare Source

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!

v0.9.110: cargo-nextest 0.9.110

Compare Source

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.

v0.9.109: cargo-nextest 0.9.109

Compare Source

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.

v0.9.108: cargo-nextest 0.9.108

Compare Source

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.

v0.9.106: cargo-nextest 0.9.106

Compare Source

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.

v0.9.105: cargo-nextest 0.9.105

Compare Source

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!

v0.9.104: cargo-nextest 0.9.104

Compare Source

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.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.