-
Notifications
You must be signed in to change notification settings - Fork 275
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
AFLChurn++ Experiment #2012
AFLChurn++ Experiment #2012
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Hi @Dammo3, I've enabled the CIs. /gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name <date-exp-name> --fuzzers <fuzzers> --benchmarks <benchmarks> E.g., /gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-08-06-aflchurn --fuzzers aflchurn aflchurnplusplus --benchmarks bloaty_fuzz_target More details of the args can be found here. |
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-08-07-aflchurnplusplus --fuzzers afl aflplusplus aflchurnplusplus |
Just a minor note: There is no need to include the baseline fuzzers in the experiment request, because FuzzBench will automatically merge their recent results in your report. |
Experiment |
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-08-07-aflchurnplusplus --fuzzers aflchurnplusplus |
Hi,
I have added two fuzzers: AFLChurn and AFLChurn++
AFLChurn is built off AFL, and AFLChurn++ is built of AFL++, so I've pretty much copied the respective integration files
I haven't been able to successfully test them locally so at the moment I'm just hoping the CI can help me identify any issues