code_coverage: introduce strategies to improve coverage
After some investigation, I figured that we were very often not running
the whole corpus against a given fuzzer, but were often stopping at the
first crash. Those crashes seem to happen often on all different
corpuses (libfuzzer, fuzzilli and centipede). Because of this, we're
missing most coverage for the various existing fuzzers.
This code still tries to keep the running time as low as possible by
removing outliers from the fuzzing targets (those that are always or
almost always constantly failing).
Bug: 409238890
Change-Id: Id76573cd12ee24ae0c6fb0ea8c3d24fb2cd6478a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6439355
Commit-Queue: Paul Semel <[email protected]>
Reviewed-by: Ali Hijazi <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1445333}
NOKEYCHECK=True
GitOrigin-RevId: af8d064c5e1136059c9410153b05c52558a07f12
1 file changed
