clusterfuzz
clusterfuzz copied to clipboard
google
Scalable fuzzing infrastructure.
### Motivation This PR addresses issues with excessive log volumes filling disks and making fuzzing jobs unable to run. It also adds basic unit tests for the fuzztest engine. ###...
They are currently being run on the proprietary google code clusterfuzz. I think schedule_impact_tasks is responsible.
This will allow the untrusted worker to access the builds without special handling. Fixes: https://github.com/google/clusterfuzz/issues/3957
- Removing cron jobs migrated to k8s workloads. - Adding missing REDIS_HOST in k8s workflows yaml definitions. Without this, [envsubst](https://github.com/google/clusterfuzz/blob/master/src/local/butler/deploy.py#L468) will not work and workload jobs will fail. - Adding...
On https://clusterfuzz.com/testcase-detail/6277724940206080 the date where the report will be automatically closed is before the date on which it was opened.
i apparently cannot figure out how to take over a PR so making a new one addressed comments left on https://github.com/google/clusterfuzz/pull/3902 and updated wording, fixed styling/made minor changes
Add support for: - fuzz target weights, i.e. `FuzzTargetJob` db entries - notably including `fuzz-target set` - listing `FuzzerJobs` entries in text format Rework the command-line interface: - rename data...
We'll do this by uploading *new* custom builds to a bucket that the untrusted worker can read from. We'll only do this in projects that will use untrusted workers. This...