jonathanmetzman

See https://bugs.chromium.org/p/chromium/issues/detail?id=1268969 for example.

ClusterFuzz adds testcases to the corpus that weren't produced by the fuzzer

1

@afd reports the following to me: ``` I have a fuzzer that uses a custom mutator, and it relies on the fact that no other mutators run - i.e., it...

ClusterFuzz fuzzes old builds

2

This presents a problem when ClusterFuzz expects the fuzzer binary to be different. For example, a bunch of errors are being thrown that look similar to this: ``` Command: /mnt/scratch0/clusterfuzz/bot/builds/clusterfuzz-builds-afl_envoy_13d8ff3fd8b6e12ff5bbd32d951c40c9e1c6513f/revisions/afl-fuzz...

1. Go to https://oss-fuzz.com/fuzzer-stats?group_by=by-day&date_start=2021-02-25&date_end=2021-03-03&fuzzer=libFuzzer&job=libfuzzer_asan_valijson&project=valijson 2. Log link is https://oss-fuzz.com/gcs-redirect?path=gs%3A%2F%2Fvalijson-logs.clusterfuzz-external.appspot.com%2FlibFuzzer_valijson_fuzzer%2Flibfuzzer_asan_valijson 3. Should probably be: https://oss-fuzz.com/gcs-redirect?path=gs%3A%2F%2Fvalijson-logs.clusterfuzz-external.appspot.com There's not really a good answer on what it should be. And this is a minor...

This will improve go's native fuzzer.