Conversation
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-04-07-aflpp --fuzzers aflplusplus_early aflplusplus_last |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-04-07-aflpp2 --fuzzers aflplusplus_early aflplusplus_last |
|
@DonggeLiu I have big troubles getting the benchmarks working. locally for me everything compiles fine, e.g. re2_fuzzer: but when building here I get and that makes no sense because for one fuzzer the same two targets always build on fuzzbench (ossfuzz, openh264), and all other fail. but the other fuzzer instance succeeds in all targets. and the only difference between the two in builder.Dockerfile is: do you have any idea what is going wrong? |
Could flaky network issues cause this? In the past, I recall seeing |
|
I have this issue since Friday. And if it would be a network issue it would affect both fuzzers and random targets |
|
And you can see it works in the ci too - it’s green for most |
I see. That's strange because I don't recall changing anything related last week. For now, I can:
Meanwhile, I guess two potential ways may help us understand this error better:
|
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-04-08-aflpp --fuzzers aflplusplus_early aflplusplus_last |
|
Same in your run. Ci is green for the targets, but for the fuzzing the same fuzzer only one target built successfully :( the test is important because this is testing a major change for llvm 16+ and we need a release very soon |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-04-08-aflpp3 --fuzzers aflplusplus_early aflplusplus_last |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-04-09-aflpp --fuzzers aflplusplus_early aflplusplus_last |
|
@DonggeLiu it worked when I switched to llvm 16 (or the issue just dissolved for other reasons). trying llvm 19 now. |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-04-09-aflpp2 --fuzzers aflplusplus_early aflplusplus_last |
|
I'm guessing the differences between this happening in prod vs local are because of caching. |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-05-18-aflpp --fuzzers aflpp aflpp2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-05-19-aflpp --fuzzers aflpp aflpp2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-05-20-aflpp --fuzzers aflpp aflpp2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-05-23-aflpp --fuzzers aflplusplus aflplusplus_weight0 aflplusplus_weight1 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-05-24-aflpp --fuzzers aflplusplus aflplusplus_weight0 aflplusplus_aweight0 aflplusplus_aweight1 --benchmarks bloaty_fuzz_target curl_curl_fuzzer_http freetype2_ftfuzzer harfbuzz_hb-shape-fuzzer jsoncpp_jsoncpp_fuzzer lcms_cms_transform_fuzzer libjpeg-turbo_libjpeg_turbo_fuzzer libpcap_fuzz_both libpng_libpng_read_fuzzer libxml2_xml libxslt_xpath mbedtls_fuzz_dtlsclient openh264_decoder_fuzzer openssl_x509 openthread_ot-ip6-send-fuzzer proj4_proj_crs_to_crs_fuzzer re2_fuzzer sqlite3_ossfuzz stb_stbi_read_fuzzer systemd_fuzz-link-parser vorbis_decode_fuzzer woff2_convert_woff2ttf_fuzzer zlib_zlib_uncompress_fuzzer |
|
@jonathanmetzman this is what I meant with the issues I have on fuzzbench: Everything built fine for https://www.fuzzbench.com/reports/experimental/2024-05-23-aflpp/index.html in https://www.fuzzbench.com/reports/experimental/2024-05-24-aflpp/index.html I didn’t change these but added two more. The ones I added are fine but the original two now have one target that didn’t built. I didn’t check the build logs what exactly went wrong but either way it is something that fuzzbench should detect and retry, wiping a cache beforehand etc or whatever is causing this. |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-22-aflpp2 --fuzzers aflplusplus3 aflplusplus2_havoc |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-24-aflpp --fuzzers aflplusplus2_nocmplog aflplusplus5 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-24-aflpp2 --fuzzers aflplusplus2_nocmplog aflplusplus5 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-23-libafl --fuzzers aflplusplus2 libafl_fuzz |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-24-aflpp3 --fuzzers aflplusplus2_nocmplog aflplusplus5 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-23-libafl2 --fuzzers aflplusplus2 libafl_fuzz |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-25-aflpp --no-seeds --fuzzers aflplusplus2 aflplusplus2_fs aflplusplus2_fs2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-24-aflpp4 --fuzzers aflplusplus5 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-26-aflpp --no-seeds --fuzzers aflplusplus2_fs aflplusplus2_fs2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-27-aflpp --fuzzers aflplusplus2 aflplusplus2_map1 aflplusplus2_map2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-28-aflpp --fuzzers aflplusplus2 aflplusplus2_map1 aflplusplus2_map2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-28-aflpp-fs1 --no-seeds --fuzzers aflplusplus2_fs aflplusplus2_fs1 aflplusplus2_fs2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-28-aflpp-fs2 --oss-fuzz-corpus --fuzzers aflplusplus2_fs aflplusplus2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-30-aflpp --fuzzers aflplusplus2_map1 aflplusplus2_map2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-01-31-aflpp --no-seeds --fuzzers aflplusplus2_fs aflplusplus2_fs1 aflplusplus2_fs2 |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-02-03-aflpp --fuzzers aflplusplus_87d26ff7 aflplusplus_2f547189 aflplusplus_2e398291 aflplusplus_f9f83b91 --benchmarks lcms_cms_transform_fuzzer openthread_ot-ip6-send-fuzzer |
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2026-02-04-aflpp --fuzzers aflplusplus_2b7524cb aflplusplus_72527a --benchmarks openthread_ot-ip6-send-fuzzer |
No description provided.