-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
windows-tests: Update connectivity check util function #117721
windows-tests: Update connectivity check util function #117721
Conversation
Sometimes, the kube-proxy endpoints take longer than 10 seconds to be ready, so the initial connection check fails (via `gomega.Eventually`). This patch uses a separate longer timeout for `gomega.Eventually`. Signed-off-by: Ionut Balutoiu <ibalutoiu@cloudbasesolutions.com>
Hi @ionutbalutoiu. 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. |
More info about this change in the PR #98499 (comment). |
/cc @jsturtevant, @marosset |
There is an explanation for this change in #98499 (comment). Adding a longer timeout is worth a try. /lgtm |
LGTM label has been added. Git tree hash: 4d772da20ada87db9785690563fc021465604135
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ionutbalutoiu, marosset 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 type of PR is this?
/kind flake
/sig testing
/sig windows
What this PR does / why we need it:
Sometimes, the Windows kube-proxy endpoints take longer than 10 seconds to
be ready, so the initial connection check fails (via
gomega.Eventually
).This patch uses a separate longer timeout for
gomega.Eventually
.Which issue(s) this PR fixes:
Related: #98499
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: