Fix fuzzer to include instrumentation#965
Merged
Julian merged 1 commit intopython-jsonschema:mainfrom Jun 8, 2022
Merged
Conversation
Member
|
Thanks! |
DavidKorczynski
added a commit
to DavidKorczynski/oss-fuzz
that referenced
this pull request
Jun 9, 2022
AdamKorcz
pushed a commit
to google/oss-fuzz
that referenced
this pull request
Jun 9, 2022
MartinPetkov
pushed a commit
to MartinPetkov/oss-fuzz
that referenced
this pull request
Aug 15, 2022
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
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.
I noticed the fuzzer has been broken for a while (https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=37327) and this should fix it. It's related to some updates in Atheris -- I believe since this commit google/atheris@0fb69ec
Another interesting update on the OSS-Fuzz side is that it now builds with code coverage. So once the fuzzer starts running again we should be able to see visualise how much of the code has been explored (by visiting https://oss-fuzz.com).