Crash Centipede on setup failure and prune old crash inputs with setup failures. #1539
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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
cl/721812896
branch
2 times, most recently
from
d09326c to
eb4b36d
Compare
…p failures. Note: We currently don't crash on setup failures that involve exceeding resource limits, e.g., timeouts or OOMs. Doing that requires connecting the Centipede watchdog with the FuzzTest runtime to be able to pass information about the crash type (currently the watchdog directly dumps the crash type to a file and has no way of knowing whether we're in the test setup or executing an input). PiperOrigin-RevId: 722744618
copybara-service
bot
force-pushed
the
cl/721812896
branch
from
eb4b36d to
1752ee0
Compare
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.
Crash Centipede on setup failure and prune old crash inputs with setup failures.
Note: We currently don't crash on setup failures that involve exceeding resource
limits, e.g., timeouts or OOMs. Doing that requires connecting the Centipede
watchdog with the FuzzTest runtime to be able to pass information about the
crash type (currently the watchdog directly dumps the crash type to a file and
has no way of knowing whether we're in the test setup or executing an input).