{{ message }}
ci: bound Go fuzzing by execution count - #13757
Merged
Merged
Conversation
Go can report context deadline exceeded when a duration-based fuzz limit expires (https://go.dev/issue/75804). Use a 50,000-execution limit based on the roughly 47,000 executions FuzzImageStore completed in 30 seconds in CI. This keeps work stable across runners and avoids the duration issue. Assisted-by: Codex Signed-off-by: Chris Henzie <chrishenzie@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts the go test -fuzz CI helper to use an execution-count bound instead of a duration bound, avoiding intermittent context deadline exceeded failures when duration-based limits expire (per go.dev/issue/75804).
Changes:
- Switch fuzzing limit from a fixed duration (
60s) to a fixed execution count (50000x). - Update script documentation to reflect the new limit and link the upstream Go issue motivating the change.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
dmcgowan
approved these changes
Jul 12, 2026
mxpv
approved these changes
Jul 12, 2026
Member
Author
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.

Go can report context deadline exceeded when a duration-based fuzz limit expires (https://go.dev/issue/75804).
Use a 50,000-execution limit based on the roughly 47,000 executions FuzzImageStore completed in 30 seconds in CI. This keeps work stable across runners and avoids the duration issue.
Assisted-by: Codex