Added
-
Nextest now provides a JSON Schema for repository configuration at
.config/nextest.toml, enabling validation and IDE autocompletion via the Tombi language server.Thanks ya7010 for your first contribution, and for maintaining Tombi!
(Note that the Taplo language server is not supported due to a crash bug. The schema has been tested to work with Tombi.)
-
For target triples that nextest doesn't have built-in information about, nextest now invokes
rustc --print=cfg --target=<triple>to resolve platform information before falling back to heuristic detection. This is particularly useful for custom builds of the Rust toolchain. (#3331)Thanks mhatzl for your first contribution!
Changed
-
User config platform overrides are now always evaluated against the build target: the platform nextest was compiled for. Previously, the build target was used in some cases and the host platform in others. (#3285)
In most cases the build target matches the host platform, but they can differ when, for example, running an
x86_64-unknown-linux-muslnextest binary on a glibc (-gnu) host. This change does not affect per-test overrides, which continue to be matched against the host or target platform of the tests being run.
Fixed
cargo nextest store exportandcargo nextest store export-chrome-tracenow verify the store format version before exporting, matching the behavior ofcargo nextest replayand the rerun commands. (#3287)