Skip to content
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

Bump up integration2 k8s istio deployment timeout duration. #12482

Closed
wants to merge 1 commit into from

Conversation

incfly
Copy link

@incfly incfly commented Mar 14, 2019

Why it's 900 seconds, from a previous run,
https://storage.googleapis.com/istio-prow/pr-logs/pull/istio_istio/12481/istio-integ-k8s-tests/4954/build-log.txt

2019-03-13T22:59:55.880239Z info CI Checking pods...
2019-03-13T23:11:03.394889Z info CI === SUCCEEDED: Deploy Istio ===

First Checking pods and finally SUCCEEDED, it's 12 minutes. 900 secs is 15min for safer.

Hopefully once we get #12274 landed, this can be faster.

@istio-testing
Copy link
Collaborator

@incfly: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
prow/e2e-simpleTests-cni.sh 1a0e20f link /test e2e-simpleTests-cni
prow/istio-integ-k8s-tests.sh 1a0e20f link /test istio-integ-k8s-tests
prow/e2e-mixer-no_auth.sh 1a0e20f link /test e2e-mixer-no_auth
prow/istio-pilot-multicluster-e2e.sh 1a0e20f link /test istio-pilot-multicluster-e2e

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.

@nmittler
Copy link
Contributor

@incfly do we know why it's taking so long on prow? Do we have limited resources available?

@esnible
Copy link
Contributor

esnible commented Mar 15, 2019

@nmittler See #11904 and #11593 and #12431 . Builds using my PR do kubectl describe on pods when tests fail; I noticed the problem was

Warning  FailedScheduling  44s (x57 over 16m)  default-scheduler  0/1 nodes are available: 1 Insufficient cpu.

My PR has gone stale. My hope is that it gets merged to Master soon.

@ozevren
Copy link
Contributor

ozevren commented Mar 15, 2019

/lgtm

@istio-testing
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: incfly, ozevren

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@istio-testing istio-testing added approved needs-rebase Indicates a PR needs to be rebased before being merged labels Mar 15, 2019
@istio-testing
Copy link
Collaborator

@incfly: 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.

@ozevren
Copy link
Contributor

ozevren commented Mar 20, 2019

@incfly Can we close this PR? The new framework uses 20 minutes for the time being, until #12606 can be resolved.

@incfly
Copy link
Author

incfly commented Mar 21, 2019

Yeah, we can close it given the tests are passing stably now.

@incfly incfly closed this Mar 21, 2019
@incfly incfly deleted the k8s-test-longer branch April 16, 2019 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-rebase Indicates a PR needs to be rebased before being merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants