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
e2e: increase targetNamespace timeout 30s=>3m #1799
Conversation
30s wasn't a reasonable amount of time to expect to get all the way from Deployment to a completed reconcile loop, and we've been seeing a lot of CI flakes as a result.
/assign @abutcher |
cc @abraverm -- this was probably the cause of all those flakes you started seeing. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 2uasimojo, abutcher 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 |
/test e2e but this looks like it might be real? |
@2uasimojo: 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. |
Force-merging this so #1802 can land (and unwedge CI) without annoying flakes. |
30s wasn't a reasonable amount of time to expect to get all the way from
Deployment to a completed reconcile loop, and we've been seeing a lot of
CI flakes as a result.