fake clock: expose the number of waiters #325
Merged
+82
−2
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.
By using
Waiters()
, tests can wait until the expected number of waiters are present before manipulating the clock's time, ensuring that the goroutine under test has reached a stable state regarding its timers./kind feature
/kind flake
What this PR does / why we need it:
When working on kubernetes/kubernetes#131502 it took me a while to find the source of flakiness, the code under test uses two timers and runs in a goroutinge.
There is a race between the test code when updating the fake clock time, that may happen before the timers are reset.
The fake clock already has the
HasWaiters()
method, but that only works for one timer, leaving a small window for the race to happen. In order to avoid that, we need to expose the actual number of waiters to be able to synchronize the test .Release note:
/assign @thockin @danwinship