van Hauser

that is a fuzzbench issue I have seen before. once the run is finished it will pop up, 1-2 more days.

the report is up but no kfuzz fuzzer results are displayes :-( ... I am downloading the logs and checking what the issue is.

Here are the raw coverage results (only completed runs): ``` bloaty_fuzz_target.TXT ======================= aflplusplus2 8.33% aflplusplus2 8.20% aflplusplus2 8.26% aflplusplus2 8.11% aflplusplus2 8.31% aflplusplus2 8.25% aflplusplus2 8.29% aflplusplus2 8.22% aflplusplus2 8.11%...

a quick look shows that kfuzz2 is better than kfuzz1, however I do not see a noticable difference between kfuzz2 and aflplusplus

for whatever reason this is running with a visible intermediate report: https://www.fuzzbench.com/reports/experimental/2024-10-25-aflpp/index.html should have useful results in about 50 hours.

Maybe you compared against an afl++ commit on fuzzbench that was buggy or a change you did degraded performance. Don’t give up :)

I made a new run with kfuzz2 as currently the google cloud seems to be more stable, and voila it runs with intermediate results: https://www.fuzzbench.com/reports/experimental/2024-10-27-aflpp/index.html will take another 48 hours...

The new results are much better for kfuzz now, but they are basically equivalent to afl++

@rajRishi22 : @ogechno is working on it he said (I just asked him). If he does not submit a PR until the new year then feel free to submit something...

/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2025-03-27-fixseed --fuzzers aflplusplus-fixseed1 aflplusplus-fixseed2 aflplusplus-fixseed3 aflplusplus-fixseed4 aflplusplus-fixseed5