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
Automated cherry pick of #38814 #39079 release 1.5 #39137
Automated cherry pick of #38814 #39079 release 1.5 #39137
Conversation
jszczepkowski
commented
Dec 22, 2016
•
edited
edited
Fixed infinite loop in cluster validation when getting nodes failed.
Fixed cluster validation in multi-zone mode: added -q and project flags to gcloud.
Jenkins Bazel Build failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins GCI GKE smoke e2e failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE etcd3 e2e failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE Node e2e failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins GCI GCE e2e failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins unit/integration failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE e2e failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins Kubemark GCE e2e failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins CRI GCE Node e2e failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins verification failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Jenkins GKE smoke e2e failed for commit d80d59c. Full PR test history. The magic incantation to run this job again is |
Please rebase |
@saad-ali |
@kubernetes/test-infra-maintainers Any idea why the submit queue is not picking up this PR? All checks look green:
|
@k8s-bot bazel test this |
@saad-ali you figured it out, but SQ actually tells you, though for some reason you have to click on the "PRs" tab: http://submit-queue.k8s.io/#/prs?prDisplay=39137&historyDisplay=39137 |
Ah, the link on GitHub is subtly wrong. kubernetes-retired/contrib#2232 to fix. |
Oh, I suggest merging this by hand. kubernetes/test-infra#1436 added the ability to only run tests against certain branches, but it doesn't even set a green checkmark. I'll make a fix today. |
@k8s-bot bazel test this |
OK, it says "Skipped" now :) |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |