Revert "Work around nextest macro lib compatibility bug" #1376
Conversation
This file contains 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
|
Thanks a lot for your help! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
cargo-nextest 0.9.71 has been released, which contains the fix in nextest-rs/nextest#1499 for nextest-rs/nextest#1493.
As confirmed on nextest's own CI--and for this project in runs on my fork before and after the new
cargo-nextestrelease--this makes it so the workaround in this repository'stest-fastCI job, introduced in #1372, is no longer necessary.Since that change made the workflow slightly more complicated and was intended as temporary, this PR reverts #1372.