Repository navigation
ci(fuzz): tolerate Go's spurious -fuzztime deadline failure - #14
Merged
Merged
Conversation
The 2026-11-04 nightly failed FuzzDecodeDR with "context deadline exceeded" at the 5m -fuzztime mark, at a steady exec rate and with no failing input written: golang/go#75804, fixed for Go 1.28. make fuzz now runs scripts/fuzz.sh, which treats exactly that result as a pass and still fails on a written failing input or any other failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Why
Nightly run 41809809603 failed
FuzzDecodeDRwithcontext deadline exceededat exactly the 5m-fuzztimemark:This is the Go toolchain bug golang/go#75804, fixed for Go 1.28. The run used Go 1.26.10, and the four earlier nightlies passed.
What
make fuzznow runsscripts/fuzz.sh. It runs the same per-target loop, but a target that fails withcontext deadline exceededand wrote no failing input (Failing input written to) counts as a pass, with a notice.TESTING.mddocuments the workaround and says to remove it once the minimum Go version is 1.28.Fuzzing stays on; other projects disabled it instead (e.g. sigstore/rekor#2867).
Verified
make fuzz FUZZTIME=1s: all 23 targets pass through the script.gochecked each outcome:make checkgreen.🤖 Generated with Claude Code