Open catenacyber opened 2 years ago
The duration should come from FUZZ_SECONDS // fuzzers_left_to_run
as you mention. How long should get allocated according to your FUZZ_SECONDS
and how long does it take locally to run?
Well, I am not sure which fuzz target times out in the first place.
I get
> time ./src/fuzz_predefpcap_aware -merge=1 newdir/ suricata-cfl/corpus/fuzz_predefpcap_aware/
...
MERGE-OUTER: succesfull in 1 attempt(s)
MERGE-OUTER: the control file has 1107636 bytes
MERGE-OUTER: consumed 0Mb (66Mb rss) to parse the control file
MERGE-OUTER: 2855 new files with 47996 new features added; 11297 new coverage edges
real 1m25,703s
user 1m14,068s
sys 0m7,640s
I guess the log should tell me the command which timed out and the timeout it used
Getting logs like
Increasing
FUZZ_SECONDS
does not seem to be enough to fix this... But I seefuzz_seconds // fuzzers_left_to_run
so maybe this fuzzer is a bit long but it should have more time than the others...