jonathanmetzman

They are causing some scaling issues that need to be addressed. Disable them temporarily and then replace with something that works.

https://pantheon.corp.google.com/errors/detail/CMDozKHgzoCLzQE;service=;version=;time=PT6H?e=-13802955&mods=logs_tg_prod&project=google.com:cluster-fuzz https://pantheon.corp.google.com/errors/detail/CKOVw8L-wf7nKQ;service=;version=;time=P7D?project=google.com:cluster-fuzz&e=-13802955&mods=logs_tg_prod

Figure out what do with lcamtuf's email address

1

Emailing [email protected] is no longer the correct way to raise issues about AFL, in part because I don't think this email email address is active anymore (see #30) for example....

We probably should probably at least add the configs we use in Chrome in OSS-Fuzz, ie: building AFL with latest clang and using `trace-pc-guard`.

There's a false positive.

Squash MSAN false positives

11

Some of these may have been caused by the compiler roll. CC @maflcko

Remove wycheproof support.

1

It was never used and there are no current plans to finish this project.

Clean up clang roll https://github.com/google/oss-fuzz/pull/11714

1

- [ ] Enable "function" sanitizer.

gitpython: Failing on every run

3

I think the solution is to bundle git. I don't think we have git on our clusterfuzz instances. It's failing with this error: ``` Traceback (most recent call last): File...