clusterfuzz
clusterfuzz copied to clipboard
Scalable fuzzing infrastructure.
It's slowness is a major source of pain when updating oss-fuzz. We should give the instance running more cores and make more quota available for it.
We apparently had a drop in succesful batch runs from #4000 and subsequent PRs, so reverting for good measure
This is a prelude to fixing type errors in `environment.py`. One of the big sources of type errors so far has been the fact that `environment.get_value()` is ~untyped. Many places...
Some fuzzers will not be trusted.
pipenv has caused a lot of issues for us (in multiple projects, not just clusterfuzz). These range from speed, format stability, and transparency of errors. There are better alternatives. -...
Fuchsia is not a public facing deployment, so it makes more sense to have it in our internal configuration repository.
This breaks appengine imports ``` | src/clusterfuzz/_internal/tests/appengine/handlers/testcase_detail/mark_unconfirmed_test.py:23:0: C0411: third party import "from handlers.testcase_detail import mark_unconfirmed" should be placed before "from clusterfuzz._internal.datastore import data_types" (wrong-import-order) | src/clusterfuzz/_internal/tests/appengine/handlers/testcase_detail/mark_unconfirmed_test.py:24:0: C0411: third party import...
We are getting rid of the rss limit for chromium because their libfuzzer targets use too much memory.