libfuzzer can use a "corpus" to re-use knowledge about a program to quickly fuzz. We upload our corpus after execution. We should tolerate if we're the first run of the fuzzer on a new branch, and accept that we don't have a pre-existing corpus.
- causes
-
SERVER-77891 Use 'optional' flag to s3.get to acquire libfuzzer corpus
- Closed
- is depended on by
-
SERVER-77248 Add fuzz testing for ESC and ECOC values
- Backlog
- related to
-
SERVER-77869 op_msg_fuzzer should disable global logging
- Closed