Before we were running the fuzzing test on a dedicated dev machine. We live in 2022 and we want to offload this to a Github action via ClusterFuzzLite. This has the additional advantage that docker images for fuzzing are managed for us. Currently this boils down to the fantastic LLVM's libfuzzer.
The disadvantage is that PRs now take 10+ minutes (I assume we can bypass the longer checks for PRs that don't touch code).
Before we were running the fuzzing test on a dedicated dev machine. We live in 2022 and we want to offload this to a Github action via ClusterFuzzLite. This has the additional advantage that docker images for fuzzing are managed for us. Currently this boils down to the fantastic LLVM's libfuzzer.
The disadvantage is that PRs now take 10+ minutes (I assume we can bypass the longer checks for PRs that don't touch code).
Followed https://google.github.io/clusterfuzzlite/running-clusterfuzzlite/github-actions/