jonathanmetzman
jonathanmetzman
>FWIW, i really don't understand why must the oss-provided versions be used, or why they are provided at all. If everyone is on the same clang then we know we...
> Is there any update here? This situation is really unfortunate since at this point OSS-Fuzz is literally the only thing holding us back from using functionality that could enable...
And reopen this if it's still happening please.
Since we're planning on revamping this integration, can you just delete the Dockerfile and build.sh, so that accepting the changed version will be smoother?
We don't think this is a great candidate for OSS-Fuzz. Maybe you'd like to use [ClusterFuzzLite](https://google.github.io/clusterfuzzlite/) instead? We have gitlab support.
Who are some prominent users?
Can you share the link where you saw this: `Unknown Jazzer.js option 'coverageDirectory' or Unknown Jazzer.js option 'coverageReporters` ?
/gcbrun trial_build.py javascript --fuzzing-engines none --sanitizers none coverage
/gcbrun trial_build.py java --fuzzing-engines libfuzzer --sanitizers coverage
Is this PR still relevant?