🔧 chore(ci): retry fuzz jobs once on the deadline-exceeded shutdown flake - #207
Conversation
…lake The Go fuzzing coordinator sometimes misses its worker shutdown deadline right at -fuzztime expiry, failing the job with a bare 'context deadline exceeded' and no crasher input written. Retry once, only when that exact signature matches: deadline message in the output AND nothing new under testdata/fuzz/. A real finding always writes a crasher file, so real failures still fail on the first run. Closes #198
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 59 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Single sync commit on top of main carrying the dev/v1.6 tip tree (9d8ea57): 🔒 security(exec): bounded exec-inspect response decode (#208) 🧪 test(integration): portwing/drydock preset conformance suites (#210) 🧪 test(ci): weekly engine-matrix integration workflow (#209) 🔧 config(ci): fuzz deadline-flake retry (#207) 🔧 chore(conformance): mktemp scratch dir + live /events + trigger contracts (#206, #212) 🔧 chore(release): GA promotion — changelog, README, chart, website (#213)
Single sync commit on top of main carrying the dev/v1.6 tip tree (de8015b): 🔒 security(exec): bounded exec-inspect response decode (#208) 🧪 test(integration): portwing/drydock preset conformance suites (#210) 🧪 test(ci): weekly engine-matrix integration workflow (#209) 🔧 config(ci): fuzz deadline-flake retry + exit-status propagation (#207, #215) 🔧 chore(conformance): mktemp scratch dir + live /events + trigger contracts (#206, #212) 🔧 chore(release): GA promotion — changelog, README, chart, website (#213, #215)
Single sync commit on top of main carrying the dev/v1.6 tip tree (de8015b): 🔒 security(exec): bounded exec-inspect response decode (#208) 🧪 test(integration): portwing/drydock preset conformance suites (#210) 🧪 test(ci): weekly engine-matrix integration workflow (#209) 🔧 config(ci): fuzz deadline-flake retry + exit-status propagation (#207, #215) 🔧 chore(conformance): mktemp scratch dir + live /events + trigger contracts (#206, #212) 🔧 chore(release): GA promotion — changelog, README, chart, website (#213, #215)
1 participant
Closes #198.
The Go fuzzing coordinator sometimes misses its worker shutdown deadline right at -fuzztime expiry, failing the job with a bare 'context deadline exceeded' and no crasher written (#191 run 31016364088, #197 run 31035393351). The fuzz step now retries once, only when that exact signature matches: the deadline message in the output AND nothing new under testdata/fuzz/. A real finding always writes a crasher file, so real failures still fail on the first run — which is the distinction #198 wanted preserved.
actionlint passes (the one pre-existing SC2034 at line 146 is untouched).