Releases: nextest-rs/nextest
nextest-runner 0.56.1
See the changelog for cargo-nextest 0.9.72.
nextest-runner 0.56.0
See the changelog for cargo-nextest 0.9.71.
nextest-metadata 0.11.0
Added
RustBuildMetaSummary
now has a newplatforms
field, which contains information about host and
target platforms. This field is provided by cargo-nextest 0.9.71 and above.
Changed
- MSRV updated to Rust 1.73.
RustBuildMetaSummary::target_platforms
is now deprecated -- use
RustBuildMetaSummary::platforms
if available.
nextest-filtering 0.9.0
Changed
- MSRV updated to Rust 1.74.
- nextest-metadata updated to 0.11.0.
cargo-nextest 0.9.72
Fixed
Previously, nextest would be unable to run proc-macro tests in some circumstances:
- On Windows, with rustup 1.27.2 and above
- On all platforms, if cargo is used without rustup, or if the
cargo-nextest
binary is invoked directly
With this release, proc-macros tests now work in all circumstances. This is done by nextest detecting Rust libdirs for the host and target platforms, and adding them to the library path automatically.
(There's also the less-common case of test binaries compiled with -C prefer-dynamic
. These
situations now also work.)
See #267 and #1493 for more details.
Thanks to 06393993 for your first contribution!
Changed
As part of the above fix, libstd is now included in all archives. This makes archives around 4MB bigger, or around 8MB in cross-compilation scenarios. (It is possible to address this via config knobs -- if this is particularly bothersome to you, please post in #1515.)
cargo-nextest 0.9.71
Fixed
Previously, nextest would be unable to run proc-macro tests in some circumstances:
- On Windows, with rustup 1.27.2 and above
- On all platforms, if cargo is used without rustup, or if the
cargo-nextest
binary is invoked directly
With this release, proc-macros tests now work in all circumstances. This is done by nextest detecting Rust libdirs for the host and target platforms, and adding them to the library path automatically.
(There's also the less-common case of test binaries compiled with -C prefer-dynamic
. These
situations now also work.)
See #267 and #1493 for more details.
Thanks to 06393993 for your first contribution!
Changed
As part of the above fix, libstd is now included in all archives. This makes archives around 4MB bigger, or around 8MB in cross-compilation scenarios. (It is possible to address this via config knobs -- if this is particularly bothersome to you, please post in #1515.)
nextest-runner 0.55.0
See the changelog for cargo-nextest 0.9.69.
cargo-nextest 0.9.70
Added
-
Archives can now include extra paths in them. For example:
[profile.default] archive.include = [ { path = "my-extra-path", relative-to = "target" } ]
For more information, see Adding extra files to an archive.
Thanks to @rukai for your first contribution!
-
You can now pass in
--cargo-quiet
twice to completely discard standard error for the Cargo
commands run by nextest. This is equivalent to2> /dev/null
.
Fixed
- The initial
cargo metadata
execution now passes in--frozen
,--locked
,--offline
and--quiet
if the corresponding flags are passed into nextest. - Previously,
NEXTEST_HIDE_PROGRESS_BAR=1
did not work (onlyNEXTEST_HIDE_PROGRESS_BAR=true
did). Now both1
andtrue
work.
Changed
- Updated MSRV for compiling nextest to Rust 1.74.
cargo-nextest 0.9.69
Added
-
Archives can now include extra paths in them. For example:
[profile.default] archive.include = [ { path = "my-extra-path", relative-to = "target" } ]
For more information, see Adding extra files to an archive.
Thanks to @rukai for your first contribution!
-
You can now pass in
--cargo-quiet
twice to completely discard standard error for the Cargo
commands run by nextest. This is equivalent to2> /dev/null
.
Fixed
- The initial
cargo metadata
execution now passes in--frozen
,--locked
,--offline
and--quiet
if the corresponding flags are passed into nextest. - Previously,
NEXTEST_HIDE_PROGRESS_BAR=1
did not work (onlyNEXTEST_HIDE_PROGRESS_BAR=true
did). Now both1
andtrue
work.
Changed
- Updated MSRV for compiling nextest to Rust 1.74.
cargo-nextest 0.9.68
This is a maintenance release with many internal improvements, and preparation for future features.
Changed
-
Nextest binaries now ship with symbols, producing better stack traces. This is aligned with the behavior. See issue #1345 for more information.
-
Thanks to recent improvements, Miri is now significantly less taxing. As a result, nextest with Miri has been changed to use all threads by default. You can restore the old Miri behavior (run one test at a time) with
-j1
, or by setting in.config/nextest.toml
:[profile.default-miri] test-threads = 1
Rules for heavy tests and test groups will continue to be followed with Miri.
Thanks to Ben Kimock for driving the Miri improvements and updating nextest!
Misc
- The filter expression parser now uses winnow.
- get.nexte.st now uses Cloudflare rather than Netlify for hosting. See this discussion for more.