Tracking issue: Fuzzing necessary groundwork

[Ekleog-NEAR]

In order to make everything work well easily, we need to find a way to integrate cargo-bolero (for private items fuzzing) with clusterfuzz (for continuous fuzzing). Ideally PRs to bolero and clusterfuzz will land, but we can always use a fork meanwhile. The clusterfuzz PR is cosmetic.

Tasks

Beta Give feedback

1. fix: make the --jobs option actually work for libfuzzer camshaft/bolero#161
   +0
2. Add a subcommand to build a clusterfuzz tarball camshaft/bolero#162
   +0
3. feat: replace the --release flag with a generic --profile flag camshaft/bolero#163
   +0
4. also catch rust error messages that have been caught and resumed google/clusterfuzz#3216
   +0
5. also catch rust error messages that have been caught and resumed clusterfuzz#4
   enhancement +1
6. Deploy also catch rust error messages that have been caught and resumed Near-One/clusterfuzz#4
7. switch fuzzer infrastructure to use cargo-bolero finite-wasm#70
   +0
8. fix typo that led to fuzzer builds not being uploaded properly finite-wasm#71
   +0
9. make fuzzer panic message single-line finite-wasm#72
   +0
10. fix: patch libfuzzer to support jobs argument camshaft/bolero#176
    +0
11. fix: return the correct exit code following a libfuzzer failure camshaft/bolero#177
    +0

[Ekleog-NEAR]

The last non-completed change here is just a cosmetic change in clusterfuzz, and google doesn’t seem very reactive. Closing this issue, as the work here is basically done :)