-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
[k8s.io] Deployment lack of progress should be reported in the deployment status {Kubernetes e2e suite} #31697
Labels
kind/flake
Categorizes issue or PR as related to a flaky test.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Comments
Hm, why the bot is opening issues about tests not in master? :) |
@kubernetes/test-infra-admins |
@Kargakis we see a lot of flakes in our PR runs. if this was a legitimate failure in the PR, the bot shouldn't have opened an issue. |
This was referenced Nov 5, 2016
This was referenced Nov 24, 2016
This was referenced Dec 1, 2016
This was referenced Dec 11, 2016
Closed
Closed
This was referenced Dec 20, 2016
This was referenced Dec 31, 2016
This was referenced Jan 8, 2017
This was referenced Jan 20, 2017
This was referenced Jan 29, 2017
This was referenced Feb 5, 2017
This was referenced Mar 11, 2017
This was referenced Mar 23, 2017
This was referenced Apr 7, 2017
This was referenced Apr 17, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/flake
Categorizes issue or PR as related to a flaky test.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/19343/kubernetes-pull-build-test-e2e-gce/56564/
Failed: [k8s.io] Deployment lack of progress should be reported in the deployment status {Kubernetes e2e suite}
Happened on a presubmit run in #19343.
The text was updated successfully, but these errors were encountered: