feat: enable listing with cargo-nextest and a timeout #290
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.
Builds on top of #289, review only the second commit to see the changes introduced here.
This allows using nextest with a specific nextest profile, instead of cargo test. In particular, with this nextest configuration:
I'm getting the following improvements on listing fuzzers for https://github.com/agglayer/agglayer.
Before:
After:
Which is a ~3x speed improvement, without any fuzzer being missed (because fuzzers naturally reply to
CARGO_BOLERO_SELECT
in less than 500ms) 🎉I'm thinking this could be very helpful for large repos, at least until something like #196 could get implemented.
WDYT?