Add upload and download fuzz corpus to the fuzzing ci#822
Draft
Add upload and download fuzz corpus to the fuzzing ci#822
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #822 +/- ##
==========================================
- Coverage 91.50% 91.45% -0.05%
==========================================
Files 235 235
Lines 28686 28686
==========================================
- Hits 26248 26234 -14
- Misses 2438 2452 +14 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
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.
This PR introduces storage for the fuzz testing corpus using GitHub build artifacts.
Proposed Workflow
masterbranch.masterbranch during their runs.Feedback Requested
I’m looking for input on whether this is the optimal approach, specifically regarding:
masterbranch corpus for all other branches the correct way to handle seed data?mastercorpora as a seed is to ensure branches have a more deterministic build. By doing this, the corpora only changes when themasterbranch itself is updated, preventing noise from fluctuating seeds on feature branches.Any thoughts or suggestions on this setup are welcome!