ci: bound Go fuzzing by execution count by chrishenzie · Pull Request #13757 · containerd/containerd · GitHub
Skip to content

ci: bound Go fuzzing by execution count - #13757

Merged
mxpv merged 1 commit into
containerd:mainfrom
chrishenzie:fix-go-fuzz-flake
Jul 12, 2026
Merged

ci: bound Go fuzzing by execution count#13757
mxpv merged 1 commit into
containerd:mainfrom
chrishenzie:fix-go-fuzz-flake

Conversation

@chrishenzie

Copy link
Copy Markdown
Member

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

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>
Copilot AI review requested due to automatic review settings July 9, 2026 23:46
@github-project-automation github-project-automation Bot moved this to Needs Triage in Pull Request Review Jul 9, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@github-project-automation github-project-automation Bot moved this from Needs Triage to Review In Progress in Pull Request Review Jul 12, 2026
@mxpv
mxpv added this pull request to the merge queue Jul 12, 2026
Merged via the queue into containerd:main with commit ba01536 Jul 12, 2026
86 of 90 checks passed
@github-project-automation github-project-automation Bot moved this from Review In Progress to Done in Pull Request Review Jul 12, 2026
@chrishenzie
chrishenzie deleted the fix-go-fuzz-flake branch July 13, 2026 05:18
@chrishenzie chrishenzie added cherry-pick/1.7.x Change to be cherry picked to release/1.7 branch cherry-pick/2.0.x Change to be cherry picked to release/2.0 branch cherry-pick/2.2.x Change to be cherry picked to release/2.2 branch cherry-pick/2.3.x Change to be cherry picked to release/2.3 cherry-picked/1.7.x PR commits are cherry-picked into release/1.7 branch cherry-picked/2.0.x PR commits are cherry picked into the release/2.0 branch cherry-picked/2.2.x PR commits are cherry-picked into release/2.2 branch cherry-picked/2.3.x PR commits are cherry picked into release/2.3 branch and removed cherry-pick/1.7.x Change to be cherry picked to release/1.7 branch cherry-pick/2.0.x Change to be cherry picked to release/2.0 branch cherry-pick/2.2.x Change to be cherry picked to release/2.2 branch cherry-pick/2.3.x Change to be cherry picked to release/2.3 labels Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-picked/1.7.x PR commits are cherry-picked into release/1.7 branch cherry-picked/2.0.x PR commits are cherry picked into the release/2.0 branch cherry-picked/2.2.x PR commits are cherry-picked into release/2.2 branch cherry-picked/2.3.x PR commits are cherry picked into release/2.3 branch size/S

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants