-
Notifications
You must be signed in to change notification settings - Fork 264
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
Verify recent error cause #2011
Conversation
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-08-03-dg --fuzzers libfuzzer --benchmarks libxml2_xml |
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-08-03-test --fuzzers libfuzzer --benchmarks libxml2_xml |
Experiment |
weird your experiment is not coming up at https://www.fuzzbench.com/reports/experimental/index.html but is available here - https://storage.googleapis.com/www.fuzzbench.com/reports/2024-08-03-test/index.html |
@DonggeLiu I think there may be a correlation with merging results. One of my experiments (here) on 1 aug ran fine merging disabled, but the ones with merging enabled failed to run the coverage checker... I see your run up above ran fine with merging disabled too. |
Yep, I recall @jonathanmetzman has changed the logic. |
Interesting observation, thanks! |
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-08-05-test --fuzzers libfuzzer_test --benchmarks libxml2_xml |
Experiment |
Ok, bad news is it doesn't seem to be quite so simple. This failed to run with merging disabled :/ |
Yep, the experiment did not generate a report at all. |
Hi @DanBlackwell, fuzzbench/experiment/measurer/coverage_utils.py Lines 134 to 136 in d8a7723
There are also many I will cancel all experiment instances for |
Hi @DonggeLiu , I believe it's only possible to rebase onto branches in the parent repo; not PRs. As an alternative I've created a squashed patch of #2000, and you should be able to just Here's the patch file: dgfuzz_commit.patch |
I reckon clicking the Let me know if this is not available to you though, I can do it for you (if you don't mind). With that said, seeing libfuzzer works on your PR and aflpp work in #1966, I wonder if other reasons caused the failure. |
My bad, you are correct; I have rebased it now.
Hmm, is there anything in the logs for the measurer at all? |
The report shows the coverage of the fuzzer, so I presume the measurer must be running? |
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-08-07-libfuzzer-zlib --fuzzers libfuzzer --benchmarks zlib_zlib_uncompress_fuzzer |
I reckon we can conclude the error is not caused by FuzzBench infra? |
Recent PR experiments experience similar errors.
This PR intends to verify if the error is caused by our recent code changes.