Skip to content

ci(fuzz): fuzz main and v3 nightly in parallel jobs, keep the corpus (#387) - #500

Merged
adityamukho merged 1 commit into
mainfrom
fuzz/387-workflows-main
Oct 9, 2026
Merged

adityamukho merged 1 commit into
mainfrom
fuzz/387-workflows-main

Conversation

@adityamukho

Copy link
Copy Markdown
Collaborator

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 on main.

.github/workflows/fuzz.yml and the new .github/workflows/fuzz-corpus.yml are byte-identical to #498's, so future main → v3 merges don't conflict on them.

  • fuzz.yml: main at 04:00 UTC and v3 at 16:00 UTC. The cron string picks the branch, as in bench.yml/crash-kill.yml. Each target runs in its own parallel job, taken from the branch's own fuzz/Cargo.toml, so main keeps fuzzing its six v7 targets unchanged. The corpus is restored from and saved to actions/cache per branch and target. -timeout=60 catches hangs. Failures go to "Nightly fuzz failure ()".
  • fuzz-corpus.yml: weekly (Monday; main at 08:00, v3 at 20:00) cargo fuzz cmin per target. It keeps committed seed_* files, saves the result to the cache, force-pushes bot/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_dispatch run of fuzz.yml from #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.yml can only be dispatched once it is on main; I'll smoke-test it after merge.

No code or test changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_012wXxZguv7PgKQjMMH4yJ5h

…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

codecov Bot commented Oct 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@adityamukho
adityamukho merged commit b67c34a into main Oct 9, 2026
21 checks passed
@adityamukho
adityamukho deleted the fuzz/387-workflows-main branch October 9, 2026 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant