chore: Fix flaky tests with deterministic runs#4377
Merged
Conversation
Signed-off-by: Glenn Lewis <6598971+gmlewis@users.noreply.github.com>
Collaborator
Author
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4377 +/- ##
=======================================
Coverage 97.51% 97.51%
=======================================
Files 193 193
Lines 19526 19526
=======================================
Hits 19040 19040
Misses 268 268
Partials 218 218 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
stevehipwell
approved these changes
Jul 10, 2026
stevehipwell
left a comment
Contributor
There was a problem hiding this comment.
LGTM
@gmlewis as an aside did you consider using synctest to keep the timeout pattern?
Collaborator
Author
Yes, in fact the agent started out fixing this flaky test by using synctest but then discovered it could completely remove all asynchrony and make the tests fully deterministic without changing their primary objectives without it. |
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.
This PR addresses a recent race failure on Windows demonstrated here:
https://github.com/gmlewis/go-github/actions/runs/29060026853/job/86259654619
The crash was fatal error: bad g->status in ready — a Go runtime bug on Windows + -race, triggered when parallel tests with goroutines/timers complete under heavy load.
Root cause of flakiness: Two rate-limit tests relied on wall-clock timing:
Fix — made both fully deterministic with zero real-time dependencies:
Also fixed a copy-paste bug: "Expected 1 requests" → "Expected 0 requests".