-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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: use exponential backoff policy to listen on nginx.StatusPort
in unit test cases
#7131
fix: use exponential backoff policy to listen on nginx.StatusPort
in unit test cases
#7131
Conversation
Hi @tokers. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/ok-to-test
/assign |
/retest |
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.
It's green.
/lgtm
/approve Thank you! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rikatz, tao12345666333, tokers 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 |
What this PR does / why we need it:
Currently, unit test cases are run parallelly, however, some test cases might listen on the Nginx status port (
10246
) simultaneously, which broken their running.In this Pull Request, an exponential backoff policy is applied in these unit test cases, considering these test cases won't run continuously for a long while, it should be effective.
Types of changes
Which issue/s this PR fixes
#7127
How Has This Been Tested?
Checklist: