Fuzz on ClusterFuzzLite - #120
Open
LucaCappelletti94 wants to merge 2 commits into
Open
LucaCappelletti94 wants to merge 2 commits into
LucaCappelletti94 wants to merge 2 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #120 +/- ##
==========================================
- Coverage 95.33% 95.32% -0.02%
==========================================
Files 33 33
Lines 25346 25346
==========================================
- Hits 24164 24160 -4
- Misses 1182 1186 +4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
In the past, I had configured the CI fuzzer as a simple periodic run. I have since moved to ClusterFuzzLite in all of the relevant projects I maintain, like diesel and sqlparser. Both are already deployed and have already caught several real bugs.
This runs the three existing cargo-fuzz targets on ClusterFuzzLite. Every pull request gets ten minutes of fuzzing aimed at the code it changes, and a daily batch run fuzzes for an hour and keeps its corpus on a
clusterfuzzlitebranch of this repository, pruned an hour before each batch. That covers whatfuzz.ymldid on pull requests and every night, so this removes it. The OSS-Fuzz image builds tokio under AddressSanitizer on its own nightly without the compiler crash that pinnedfuzz.ymltonightly-2026-07-23. I checked the build locally through the samecompileentrypoint the action runs, then fuzzed each target for a minute.Only the batch and prune jobs request
contents: write, since they push the corpus to theclusterfuzzlitebranch. That branch is created on the first run.Related issues
I haven't opened one.
Type of change
Checklist
make before-git-pushpasses locally (check, build, format, audit, test, doc-check)--features rustls-tlsif connection/streaming code changed)Performance notes
n/a