CI: use corpus for fuzzing #432
Merged
Conversation
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
The current CI test boostraps the fuzzer every time we run the CI due to it not using any corpus. That reduces the usefulness of running fuzz on CI. Instead of just using the fuzzer like this, we should use some corpus that already have a decent coverage and will stress our code in a satisfactory way. This commit uses the corpus data provided by the floresta-qa-assets repository. It contains corpus data generated over months of continuous fuzzing.
|
In the future we should have these inputs directly inside
|
JoseSK999
approved these changes
Mar 28, 2025
I don't think we need this, since this folder can get quite big. I would download those assets only when they are need |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What is the purpose of this pull request?
Which crates are being modified?
Description
Closes #415
The current CI test boostraps the fuzzer every time we run the CI due to it not using any corpus. That reduces the usefulness of running fuzz on CI. Instead of just using the fuzzer like this, we should use some corpus that already have a decent coverage and will stress our code in a satisfactory way.
This commit uses the corpus data provided by the floresta-qa-assets repository. It contains corpus data generated over months of continuous fuzzing.
Notes to the reviewers
Checklist
just lintcargo test