Stefan Bucur

Failures in the test suite running on latest Bazel

4

See for example https://github.com/bazelbuild/rules_fuzzing/actions/runs/2522403386: ``` ERROR: Traceback (most recent call last): File "/home/runner/work/rules_fuzzing/rules_fuzzing/WORKSPACE", line 35, column 12, in jazzer_init() File "/home/runner/.cache/bazel/_bazel_runner/fe6cb6e248ce6cff4727b846eff77c1f/external/jazzer/init.bzl", line 26, column 24, in jazzer_init kotlin_repositories() File "/home/runner/.cache/bazel/_bazel_runner/fe6cb6e248ce6cff4727b846eff77c1f/external/io_bazel_rules_kotlin/src/main/starlark/core/repositories/initialize.bzl",...

Java examples broken on macOS

1

See latest failure at https://github.com/bazelbuild/rules_fuzzing/actions/runs/1809704990 @fmeum would you like to take a look?

Analysis-time tests are documented here: https://docs.bazel.build/versions/master/skylark/testing.html

Consider adding support for the bzlmod module system

1

We should figure out to to expose dependencies like Honggfuzz, and the OSSFuzz repository rules. See more at https://docs.bazel.build/versions/main/bzlmod.html

Support specifying runtime fuzzing options in the fuzz target rule.

4

The initial set of options should include the maximum input length. That seems to be referenced in a number of [fuzz targets in GRPC](https://github.com/grpc/grpc/tree/master/tools/fuzzer/options), for example.

Rather than having Bazel fail on those targets, we should have separate test rules that pass when the compilation would fail.

This way, we'll be able to implement more checks without having to grow the Github action specification too much. Candidate check: Enforce an external timeout when running the fuzzer with...