[SKIP SOF-TEST] fuzz.sh: add -jobs parameter. Switch to built-in -max_total_time. #8851
Conversation
|
Outputs in https://github.com/thesofproject/sof/actions/runs/7851518795/job/21428707809?pr=8851 look great. |
|
Brand new failure in https://github.com/thesofproject/sof/actions/runs/7868973600/job/21467150473?pr=8851? Demoting to draft for now. |
@andyross is that another panic being masked? |
There was no need to use the external "timeout" command + some complicated exit code logic, libFuzzer has that feature built-in. Switch to it and delete a few good line. Add an option to use the built-in, concurrent -jobs feature which saves a massive amount of time. It has some quirks so do not enable it by default. Decrease verbosity by default. Add in the help message the magic replay command that saves a ton of time. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Use new option to fuzz more in the same time. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
marc-hb
requested review from
jxstelter,
LaurentiuM1234,
singalsu and
iuliana-prodan
"Unit test" crash-* files allow instant reproduction. fuzz-*.log files are created when using -j Signed-off-by: Marc Herbert <marc.herbert@intel.com>
|
@marc-hb are all the dependencies in the PR message now met ? |
|
I did submit more than one PR to make debugging fuzzing issues significantly easier and faster but they are all independent of each other and can be merged in any order. This can be merged. When there are dependencies between commits I either put them in the same PR or if too big then I hold back depending PRs as drafts. |
There was no need to use the external "timeout" command + some complicated exit code logic, libFuzzer has that feature built-in. Switch to it and delete a few good line.
Add an option to use the built-in, concurrent -jobs feature which saves a massive amount of time. It has some quirks so do not enable it by default.
Decrease verbosity by default.
Add in the help message the magic replay command that saves a ton of time.
cc: