Allow multiple attempts in egress firewall test #29615
Conversation
this test is failing when using kata-containers, which might be related
to longer startup times of kata-containers:
curl: (28) Connection timed out after 1001 milliseconds
let's use the "--retry" feature of curl. This should not affect the
successful tests as they should return immediately, while it might
prolong the failing tests from 3s to 30s. With kata we need about 6-12s
so 30s should be safe for us.
Signed-off-by: Lukáš Doktor <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ldoktor The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@ldoktor: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
openshift-merge-robot
added
the
needs-rebase
|
PR needs rebase. 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-sigs/prow repository. |
this test is failing when using kata-containers, which might be related to longer startup times of kata-containers:
let's use the "--retry" feature of curl. This should not affect the successful tests as they should return immediately, while it might prolong the failing tests from 3s to 30s. With kata we need about 6-12s so 30s should be safe for us.