export seed corpus files using the SHA1 of the content as the filename #2731
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
lucas-clemente
approved these changes
Aug 25, 2020
marten-seemann
force-pushed
the
fuzzing-helper
branch
5 times, most recently
from
f4838ad
to
faa8632
Compare
The file name of that file is calculated to be the SHA1 sum of the contents.
marten-seemann
force-pushed
the
fuzzing-helper
branch
from
faa8632
to
a1c4daa
Compare
Codecov Report
@@ Coverage Diff @@
## master #2731 +/- ##
=======================================
Coverage 86.51% 86.51%
=======================================
Files 126 126
Lines 9955 9955
=======================================
Hits 8612 8612
Misses 1010 1010
Partials 333 333 Continue to review full report at Codecov.
|
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.
Content-addressing ftw. Apparently this is the convention, see https://google.github.io/oss-fuzz/getting-started/new-project-guide/#seed-corpus.
With this PR, we can now generate the corpus on the fly by running
This will create
corpus/directories, which will be used by go-fuzz.For oss-fuzz, all that's left to do is to zip the corpus directory to
<fuzztarget>.zip. We'll do that in the oss-fuzz build-script.