-
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
using --max-time instead of --connect-timeout for e2e/network/service tests. #117913
Conversation
Signed-off-by: Daman Arora <aroradaman@gmail.com>
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/cc @aojea |
/release-note-none |
/lgtm Thanks |
LGTM label has been added. Git tree hash: afdbc0f0fd8c108971be64452181907ac280393f
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, daman1807 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 |
@daman1807: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
ci-kubernetes-kind-network-ipvs-ipv6 is timing out since 5th of May. On inspection, it was found that the curl(client) gets connected but exists with error code 52. Since the client gets connected --connection-timeout won't timeout the operation and curl gets struck here, timing out the entire test suite.
This PR replaces --connection-timeout with --max-time.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: