[infra] Indicate coverage run failure when libFuzzer reports an error #13103
+14
−1
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
code is non-zero. Additionally, add a small log file to indicate the fuzzer target for which the coverage measurement did not complete succesfully. Signed-off-by: phi-go <[email protected]>
phi-go
force-pushed
the
push-qnznzrmxrksp
branch
from
c07320f to
2f85703
Compare
phi-go
changed the title
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.
Currently OOM's and timeouts for individual corpus entries during coverage measurement are silently ignored, as libFuzzer still exits with a zero returncode. This PR adds a grep for error messages during the coverage run. Additionally, add a small log file is created to indicate the fuzzer target for which the coverage measurement did not complete succesfully.