ci: add weekly deep-fuzz workflow (test:fuzz:long)#296
Closed
MauricioPerera wants to merge 1 commit into
Closed
Conversation
The fuzz tests already run on every PR inside test:unit with the default budget (50-100 runs). The deep run (FUZZ_RUNS=10000, test:fuzz:long) never runs anywhere; schedule it weekly with manual dispatch so low-probability DoS/sandbox regressions get continuous coverage without PR cost. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
@MauricioPerera is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
|
Thanks. I don't want more workflows as they increase risk |
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
2 participants
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
The fuzzing suite (
src/security/fuzzing/, 4 fuzz test files + generators + DoS/sandbox oracles) already runs on every PR insidetest:unit— but only with the default budget (50–100 runs per test,FUZZ_RUNSunset). The deep run that the repo already defines,test:fuzz:long(FUZZ_RUNS=10000), never runs in any workflow.This adds
.github/workflows/fuzz-deep.yml:workflow_dispatchfor manual runs — deliberately not on push/PR (cost).timeout-minutes: 60, setup mirroringunit-tests.yml(LFS, pnpm, Node 20), runningpnpm --filter just-bash test:fuzz:long.continue-on-error) — that's the signal.This gives low-probability DoS/sandbox regressions (only visible with a large budget) continuous coverage without adding PR latency.
Related: #295 (separate, independent change).
🤖 Generated with Claude Code