This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
check libfuzzer -help=1 prior to starting the heartbeat
#528
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
chkeita
approved these changes
Feb 10, 2021
ranweiler
approved these changes
Feb 10, 2021
ranweiler
reviewed
Feb 10, 2021
bmc-msft
commented
Feb 10, 2021
bmc-msft
commented
Feb 10, 2021
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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, the a bad libfuzzer (such as missing a prereq dll) transitions from
setting_up, torunning, then tofailure.This PR, in combination with #530, will make
--wait_for_runningactually useful in determining if the libfuzzer target is meaningfully launched.