fix: use cargo-bolero with a fix for cargo bolero list with failing tests
#10131
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
nagisa
reviewed
Nov 8, 2023
nagisa
approved these changes
Nov 8, 2023
Co-authored-by: Simonas Kazlauskas <[email protected]>
|
It currently does, I currently remember chatting with camshaft and resulting in this idea, but can’t find it again on the github issue tracker, so I just opened an issue there :) |
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.
We have tests that fail with
cargo test, and this throws offcargo bolero list, that runscargo testto list the fuzzers.With this change, we add camshaft/bolero#195, that ignores such failures and actually lists all fuzzers.
This should fix the issue, that all the latest uploads to the fuzzers bucket actually were empty tarballs.