/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:

$ make test-run-aflplusplus_early-re2_fuzzer
docker build \
--tag gcr.io/fuzzbench/builders/benchmark/re2_fuzzer \
--build-arg BUILDKIT_INLINE_CACHE=1 \
--cache-from gcr.io/fuzzbench/builders/benchmark/re2_fuzzer \
--file benchmarks/re2_fuzzer/Dockerfile \
benchmarks/re2_fuzzer
[ ] Building 12.2s (12/12) FINISHED                              docker:default
...
[*] Fuzzing test case #1848 (1882 total, 0 crashes saved, state: started :-), mode=explore, perf_score=300, weight=inf, favorite=1, was_fuzzed=0, exec_us=0, hits=0, map=337, ascii=0, run_time=0:00:00:14)...
INFO:root:Doing final sync.

but when building here I get

Step #2 - "aflplusplus_early-re2_fuzzer-builder-intermediate": #7 ERROR: executor failed running [/bin/sh -c apt-get install -y lsb-release software-properties-common gnupg wget]: exit code: 100
Step #2 - "aflplusplus_early-re2_fuzzer-builder-intermediate": ------
Step #2 - "aflplusplus_early-re2_fuzzer-builder-intermediate":  > [3/6] RUN apt-get install -y lsb-release software-properties-common gnupg wget:
Step #2 - "aflplusplus_early-re2_fuzzer-builder-intermediate": ------
Step #2 - "aflplusplus_early-re2_fuzzer-builder-intermediate": executor failed running [/bin/sh -c apt-get install -y lsb-release software-properties-common gnupg wget]: exit code: 100
Finished Step #2 - "aflplusplus_early-re2_fuzzer-builder-intermediate"
ERROR
ERROR: build step 2 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 1
------------------

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:

@@ -41,7  41,7 @@
 ENV LLVM_CONFIG=llvm-config-18
 
 # Download afl  .
-RUN git clone -b early https://github.com/AFLplusplus/AFLplusplus /afl && \
 RUN git clone -b last https://github.com/AFLplusplus/AFLplusplus /afl && \
     cd /afl && \
     true

do you have any idea what is going wrong?
btw. you can kill all afl fuzzing instances ...

ERROR: executor failed running [/bin/sh -c apt-get install -y lsb-release software-properties-common gnupg wget]: exit code: 100

Could flaky network issues cause this?

In the past, I recall seeing apt-get fail due to a network problem and then work again after a few hours in CI tests.
Maybe re-try it in a few hours and see if it occurs again?

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 have this issue since Friday. And if it would be a network issue it would affect both fuzzers and random targets

I see. That's strange because I don't recall changing anything related last week.
Unfortunately, I will need more time before I can debug this because I am currently occupied by other tasks.

For now, I can:

1. Cancel all AFL experiments, and
2. Re-launch the experiment here, just in case my account makes any difference (which is unexpected).

Meanwhile, I guess two potential ways may help us understand this error better:

1. Split the apt-get command and install one package in each. This helps us see which one caused the failure.
2. Add apt-get update && before the apt-get that caused the error. This should be unnecessary because your first RUN command already did it, but it can at least rule out a possibility.

/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 :(
And only half of the targets are there. Weird.

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.
I agree with Dongge that the issue looks like it is caused by not having apt-get update && before apt-get install

/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 2024-09-25-aflpp --fuzzers aflplusplus_nocmplog aflplusplus_vp0 aflplusplus_vp1

@DonggeLiu OK I see the same thing again - the report is not showing up.
However I see that it is running: https://storage.googleapis.com/fuzzbench-data/index.html?prefix=2024-09-25-aflpp/experiment-folders/

but it is neither here https://www.fuzzbench.com/reports/experimental/index.html nor there https://storage.googleapis.com/www.fuzzbench.com/reports/experimental/2024-09-25-aflpp/index.html

My guess is it will only be visible once the experiment is completed (which is why it showed up days later and are visible now, but not the days after I started them).
This is a new thing.

but it is neither here https://www.fuzzbench.com/reports/experimental/index.html nor there https://storage.googleapis.com/www.fuzzbench.com/reports/experimental/2024-09-25-aflpp/index.html

Is this using a lot of space?
I saw messages like Retrying on experiment.runner.TrialRunner.archive_and_save_corpus failed with [Errno 28] No space left on device. Raise.:

My guess is it will only be visible once the experiment is completed (which is why it showed up days later and are visible now, but not the days after I started them). This is a new thing.

I don't think we have changed the report upload logic. It should be the same as before.

No, nothing does create a lot of data, not more than usual.
but you see that it is running, and new report is coming up?

@DonggeLiu now that the test is completed the report is up … and two fuzzers are missing, and they produced coverage so they should be there.

Also the results look suspect - no cmplog is better than with cmplog? No …

Also the results look suspect - no cmplog is better than with cmplog? No …

I don't know the internal of AFL as well as you so I have no clue why that is better.

and two fuzzers are missing, and they produced coverage so they should be there.

Which 2 are missing?
I can search for their logs

and two fuzzers are missing, and they produced coverage so they should be there.

Which 2 are missing? I can search for their logs

aflplusplus_vp0 aflplusplus_vp1

thank you!

and two fuzzers are missing, and they produced coverage so they should be there.

Which 2 are missing? I can search for their logs

aflplusplus_vp0 aflplusplus_vp1

thank you!

@DonggeLiu reminder :) thank you!

aflplusplus_vp0 aflplusplus_vp1
thank you!

@DonggeLiu reminder :) thank you!

Thanks for pinging me.
The gcloud log does not show anything suspicious, but the fuzzer run log seem to imply some early termination problem.

gcloud Log

Taking aflplusplus_vp0 as an example, there are only 2 kinds of warning/errors, e.g.:

The error message says instance 3191872 failed to upload corpus 0037 for some reason:

But:

1. The corpus definitely exists because it can be found in the data dir.
2. There were other earlier gsutil cp errors from the same instance, which does not block the experiment.

Exp Data Dir

IIUC, the fuzzer only seems to run for < 14 hours?
The last corpus archive was created 13.5 hours after the first one.
The fuzzer log did not record anything interesting after 10 hours.

Do you happen to know the cause?
Maybe adding more logs in the fuzzer can help investigate the cause.

/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-10-17-aflpp --fuzzers aflplusplus kfuzz

/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-10-17-aflpp2 --fuzzers aflplusplus kfuzz

/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-10-18-aflpp --fuzzers aflplusplus2 kfuzz

/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-10-18-aflpp2 --fuzzers aflplusplus2 kfuzz

/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-10-21-aflpp --fuzzers aflplusplus2 kfuzz1 kfuzz2

/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-10-23-aflpp --fuzzers aflplusplus2 libafl_fuzz

@DonggeLiu I have again the issue that experimental fuzzers are not displayed in the report, not even mentioned as "not enough examples": https://www.fuzzbench.com/reports/experimental/2024-10-21-aflpp/index.html

for bloaty kfuzz1 and kfuzz2 have 10 samples each that reacher 23h. and many more that reached 22:30 etc.

I cannot work on this or the value profile feature when I do not have results I can work with :-(
Can you please help?

/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-10-25-aflpp --fuzzers aflplusplus2 kfuzz1

/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-10-27-aflpp --fuzzers aflplusplus2 kfuzz2