Repository navigation
ci(fuzz): fuzz main and v3 nightly in parallel jobs, keep the corpus (#387) - #500
Merged
Merged
Conversation
…387) Scheduled workflows run main's copy of the file, so this is what makes the nightly fuzz run reach v3. Same files as on v3 (#498): - fuzz.yml: main at 04:00 UTC, v3 at 16:00 UTC (the cron string picks the branch, as in bench.yml); one parallel job per target from the branch's own fuzz/Cargo.toml; corpus restored from and saved to the Actions cache per branch and target; -timeout=60 for hangs. - fuzz-corpus.yml: weekly cargo fuzz cmin per target, committed seed_* files kept, proposed as a pull request from bot/fuzz-corpus-<branch>. Workflow-only; no code or test changes. Refs #387 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012wXxZguv7PgKQjMMH4yJ5h
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This was referenced Oct 10, 2026
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.
Refs #387. Workflow-only companion to #498 (to
v3). Scheduled workflows run the default branch's copy of the file, so v3 is fuzzed at night only once this change is onmain..github/workflows/fuzz.ymland the new.github/workflows/fuzz-corpus.ymlare byte-identical to #498's, so futuremain→v3merges don't conflict on them.fuzz.yml:mainat 04:00 UTC andv3at 16:00 UTC. The cron string picks the branch, as inbench.yml/crash-kill.yml. Each target runs in its own parallel job, taken from the branch's ownfuzz/Cargo.toml, somainkeeps fuzzing its six v7 targets unchanged. The corpus is restored from and saved toactions/cacheper branch and target.-timeout=60catches hangs. Failures go to "Nightly fuzz failure ()".fuzz-corpus.yml: weekly (Monday;mainat 08:00,v3at 20:00)cargo fuzz cminper target. It keeps committedseed_*files, saves the result to the cache, force-pushesbot/fuzz-corpus-<branch>, and opens or updates a PR. This needs the repository setting "Allow GitHub Actions to create and approve pull requests", which is off. Until it is on, the job pushes the branch and puts a compare link in its summary.Verified: actionlint is clean. A
workflow_dispatchrun offuzz.ymlfrom #498's branch (60 s per target) ran the matrix, saved the six corpus caches, uploaded the failing target's artifact and opened the report issue. The failure was the real hang #497, and the duplicate issue #499 is closed.fuzz-corpus.ymlcan only be dispatched once it is onmain; I'll smoke-test it after merge.No code or test changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_012wXxZguv7PgKQjMMH4yJ5h