Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use cargo-nextest for running tests in CI #441

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

tgross35
Copy link
Contributor

@tgross35 tgross35 commented Jan 14, 2025

The test suite for this repo has quite a lot of tests, and it is difficult to tell which contribute the most to the long CI runtime. libtest does have an unstable flag to report test times, but that is inconvenient to use because it needs to be passed only to libtest binaries.

Switch to cargo-nextest 1 which provides time reporting and, overall, a better test UI. It may also improve test runtime, though this seems unlikely since we have larger test binaries with many small tests (nextest benefits the most when there are larger binaries that can be run in parallel).

For anyone running locally without, run.sh should still fall back to cargo test if cargo-nextest is not available.

This diff includes some cleanup and consistency changes to other CI-related files.

@tgross35 tgross35 changed the title [WIP] Use nextest Use cargo-nextest for running tests in CI Jan 14, 2025
@tgross35 tgross35 marked this pull request as ready for review January 14, 2025 02:10
The test suite for this repo has quite a lot of tests, and it is
difficult to tell which contribute the most to the long CI runtime.
libtest does have an unstable flag to report test times, but that is
inconvenient to use because it needs to be passed only to libtest
binaries.

Switch to cargo-nextest [1] which provides time reporting and, overall,
a better test UI. It may also improve test runtime, though this seems
unlikely since we have larger test binaries with many small tests
(nextest benefits the most when there are larger binaries that can be
run in parallel).

For anyone running locally without, `run.sh` should still fall back to
`cargo test` if `cargo-nextest` is not available.

This diff includes some cleanup and consistency changes to other
CI-related files.

[1]: https://nexte.st
@tgross35 tgross35 merged commit abf0a28 into rust-lang:master Jan 14, 2025
35 checks passed
@tgross35 tgross35 deleted the use-nextest branch January 14, 2025 02:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant