Migrate fuzzing to new atheris version #52080
Merged
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
Signed-off-by: David Korczynski <david@adalogics.com>
mihaimaruseac
approved these changes
Sep 23, 2021
google-ml-butler
bot
added
kokoro:force-run
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.
Signed-off-by: David Korczynski david@adalogics.com
Recently Atheris the Python fuzzer used by tensorflow-py in the OSS-Fuzz repository had an update. This has caused the fuzzers not to build in OSS-Fuzz and consequentially the fuzzers need to be re-written in the way they handle instrumentation of code. This PR fixes this.
Please see the following PR on OSS-Fuzz where the new atheris version is outlined: google/oss-fuzz#6060
Cross-referencing this PR google/oss-fuzz#6417 on the OSS-Fuzz repo as in that PR I outline the build issue in the fuzzers.