Use nextest for CI test jobs#22544
Draft
Dandandan wants to merge 1 commit into
Draft
Conversation
github-actions
Bot
added
the
development-process
Contributor
|
I think I tried this in the past ... do the ci machines have enough cores and memory to actually do this effectively? |
Contributor
|
Thank you for working on this! I’m wondering if you’ve tried connecting the |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
N/A.
Rationale for this change
Use
cargo-nextestfor CI jobs that run standard Rust test binaries so tests can execute with nextest's runner.What changes are included in this PR?
Use
cargo-nexttestAre these changes tested?
Are there any user-facing changes?
No. This only changes CI test execution.