oss-fuzz-gen
oss-fuzz-gen copied to clipboard
LLM powered fuzzing via OSS-Fuzz.
Fix[ error](https://pantheon.corp.google.com/logs/query;query=resource.type%3D%22k8s_container%22%0Aresource.labels.project_id%3D%22oss-fuzz%22%0Aresource.labels.location%3D%22us-central1%22%0Aresource.labels.cluster_name%3D%22llm-experiment%22%0Aresource.labels.namespace_name%3D%22default%22%0Aresource.labels.pod_name%3D%22daily-manual-6-qgv8f%22%20severity%3E%3DDEFAULT;cursorTimestamp=2024-02-02T07:59:28.341953276Z;aroundTime=2024-02-02T07:58:31.072Z;duration=PT10M?e=-13802955&mods=logs_tg_prod&project=oss-fuzz) and linting in `web.py`.
As we start to have many reports (from daily, one-off, pr), I wanted to use sub-directory as an easy way to visually categorize reports to keep the directory more organized....
Fixes #54 Done ~~Will also push the new benchmarks in this PR when they are ready.~~
ocasionally -> occasionally
- [x] Automatically push docker images from the PR to gcloud - [ ] Provide an easy trigger for experiments runs using the image from the PR
We need unambiguous names: Each *benchmark* should be a function, and a *project* may have multiple benchmarks/functions. For example, our current `benchmark.yaml` should be `project.yaml`. This will involve other renaming/refactoring...
Allow comparing the results (e.g., build rate, crash rate, bug discovery) against past data.