-
Notifications
You must be signed in to change notification settings - Fork 257
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
DGFuzz Integration #2000
base: master
Are you sure you want to change the base?
DGFuzz Integration #2000
Conversation
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-07-08-dgfuzz --fuzzers dgfuzz |
Ops: |
Done! Forgot about that sorry |
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-07-08-dgfuzz --fuzzers dgfuzz |
@DonggeLiu Agh, forgot to run |
Hi @DanBlackwell I've manually terminated all VM instances of that experiment and will relaunch a new one to use the latest code.
The CI checks won't block PR experiments, they are separated. |
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-07-08-dgfuzz-1 --fuzzers dgfuzz |
My apologies, I thought the
This fuzzer will only work on a subset for now, as DFSan requires all dependencies to be compiled with the |
@DonggeLiu Hmm, seems like it’s not started the experiment again (no If so, maybe it could be run with just the 8 targets that do build. I've now added dgfuzz to all the Additionally, I’ve set the If it helps, these are the 8 that build ok:
PS, if the experiment did start at some point (it's been 5 hours without starting at the time of writing), then ignore all this and let it run through :) |
I think it did : )
I don't think this will block the experiment. If this happens, then that benchmark will be excluded from the exp without affecting others. |
Hi @DonggeLiu , I've pushed up some updates - I think that last run was getting killed due to shared memory not getting freed correctly. Can you run the following:
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-07-11-dgfuzz --fuzzers dgfuzz |
Experiment |
@DonggeLiu Just a note that most of these did not build with some
From what I see it looks like |
Yep, this should be a flaky internet connection failure. |
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-07-11-dgfuzz-1 --fuzzers dgfuzz |
Experiment |
Apt is still not playing ball it seems. It's trying to fetch:
Looking here it seems there is no EDIT: it was missing |
Hi @DonggeLiu , I figured out that the issue was on my end (see comment above). In the meantime I've added a 'control' condition so that I can see how much of the improvement is down to the DFSan guidance. Could you run the following command please:
|
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2024-07-13-dgfuzz --fuzzers dgfuzz dgfuzz_control |
Experiment |
This is a new fuzzer that I'd like to test out.