test: Fix possible race in waitForNPods helper function #10481
Merged
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.
Previously,
WaitforPods()
could prematurely return whenGetPods()
returned no pods (e.g.WaitforPods()
had been immediately called after sending a create pods request).To avoid this, we should wait (by returning
false
) when the pod list is empty instead of setting theminRequired
.This makes the function to fail when a user intentionally set
minRequired
to0
inWaitforNPodsRunning()
, but I don't see any sane use case where settingminRequired
to0
would make sense.Example of such race:
Fix #10277.
This change is