-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More informative logs to help debugging #2038
base: master
Are you sure you want to change the base?
Conversation
@jonathanmetzman: |
Using KnownFuzzBench log shows the cloud build to it failed to build fuzzz target Note that the 4th log shows build config was ready in 11 AM, and the 5th log shows the cloud build command errored out ~4 hours later with return code 4-hour happens to be the timeout for executing the UnknownHowever, here is the mysterious part that I failed to understand. The Cloud Build logs shows those the cloud build 11:13 AM build succeeded in 5 min 8 sec which is within the 4 hour timeout: How come the cloud build succeeded but the It is benign so far, because another cloud build was created right after this failure at 15:15 and this time it worked. The same issue happened with But other benchmarks seem fine in the first time: AppendixThe FuzzBench log shows the glcoud command error code is
|
Another bug happened in #2028 is I will use this PR to print out more info to assist debugging. |
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-08-25-2038-libaf --fuzzers libafl |
Experiment |
Recent experiments have
Fuzz target binary not found.
errors which appears to be flaky and cannot be reproduced locally.This PR adds more logs to help understand the cause.