Dongge Liu

Restructure benchmark YAML

2

Fixes #54 Done ~~Will also push the new benchmarks in this PR when they are ready.~~

Easily trigger experiment runs based on code in a PR

6

- [x] Automatically push docker images from the PR to gcloud - [ ] Provide an easy trigger for experiments runs using the image from the PR

Distinguish `benchmark` and `project`

3

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.

Related: https://github.com/google/oss-fuzz-gen/issues/54

Convert functions in `benchmark.yaml` into a more structured way.

2

For example, from: ``` functions: - int main2(int argc, char **argv) - int scanopt_usage(scanopt_t *scanner, FILE *fp, const char *usage) project: flex target_path: /src/fuzz-main.c ``` to: ``` "functions": - "name":...

Related: #54

Update benchmarks and fuzz targets bucket periodically in GKE

3

related: #134