-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix flake in kube system test #17108
Conversation
Increase the loop range from 5 to 20 to make sure we give the service enough time to transition to inactive. Other tests have the same range with 0.5 seconds sleeps, so I expect the new value to be sufficient and consistent. Fixes: containers#17093 Signed-off-by: Valentin Rothberg <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
although I think I'd be more comfortable bumping to 10 first. @edsantiago WDYT?
I'm fine with the current bump to 20 (i.e., 10 seconds). Remember, that's only a worst-case. Given the rarity of this flake, I expect runs to take only one extra second. A fine price to pay to avoid the flake. /lgtm |
/hold cancel |
Increase the loop range from 5 to 20 to make sure we give the service enough time to transition to inactive. Other tests have the same range with 0.5 seconds sleeps, so I expect the new value to be sufficient and consistent.
Fixes: #17093
Signed-off-by: Valentin Rothberg [email protected]
Does this PR introduce a user-facing change?
@containers/podman-maintainers PTAL