[renovate]

This PR contains the following updates:

Package	Update	Change	Pending
cargo-llvm-cov	patch	0.9.0 → 0.9.1
cargo-llvm-cov	minor	0.8.7 → 0.9.1
cargo-nextest	patch	0.9.143 → 0.9.148	0.9.149
cargo-nextest	patch	0.9.140 → 0.9.148	0.9.149
cbindgen	patch	0.29.2 → 0.29.4

---

Release Notes

taiki-e/cargo-llvm-cov (cargo-llvm-cov)

v0.9.1

Compare Source

• Fix build-dir v2 path matching on Windows. (#​521, thanks @​davidkna)

nextest-rs/nextest (cargo-nextest)

v0.9.148: cargo-nextest 0.9.148

Compare Source

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!

v0.9.146: cargo-nextest 0.9.146

Compare Source

Fixed

• Updated chacha20 and der to non-yanked versions.

v0.9.145: cargo-nextest 0.9.145

Compare Source

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!

v0.9.144: cargo-nextest 0.9.144

Compare Source

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!

mozilla/cbindgen (cbindgen)

v0.29.4

Compare Source

• Support constant enums and arrays.

v0.29.3

Compare Source

• Expose the line_endings config option to use with the builder
  * Fix doc attribute parsing to properly handle block comments
  * Check for CMSE ABI's as well
  * ci: Add a meta job to block the merge queue on it.
  * Allow pub access to ReprType fields
  * In C23 mode, define sized enums as enums rather than typedefs.

---

Configuration

📅 Schedule: (UTC)

• 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 is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!