[WIP] Extend E2E Test Timeout for Flaky Tests #88
Conversation
…hould succeed This test is sometimes flaky, and possibly waiting a second we will stop get ErrorControlPlaneQuorumViolation error anymore
…hould faile This test is sometimes flaky, and possibly by waiting double the time the error won't persist
This test is sometimes flaky, and possibly by waiting double the time the error won't persist
This test is sometimes flaky, and possibly by waiting double the time the error won't persist
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: razo7 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 |
|
/retest |
razo7
changed the title
|
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/test-infra repository. |
|
@razo7: 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/test-infra repository. I understand the commands that are listed here. |
|
e2e tests are not flaky as in the past. we might revisit this PR in the future. |
NMO E2E test have been quite flaky lately, thus I was looking on the last failed PRs of NMO for OCP 4.11, 4.12, 4.13, and 4.14 (from March 16th), in order to see why the E2E tests were flaky.
There are four questionable tests that by extending there test time we might let them finish successfully: