-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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] DisruptionController should update PodDisruptionBudget status {Kubernetes e2e suite} #37176
Labels
kind/flake
Categorizes issue or PR as related to a flaky test.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
Milestone
Comments
k8s-github-robot
added
kind/flake
Categorizes issue or PR as related to a flaky test.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
labels
Nov 20, 2016
This was referenced Nov 23, 2016
This was referenced Nov 30, 2016
This was referenced Dec 13, 2016
Closed
This was referenced Dec 21, 2016
This was referenced Jan 9, 2017
This was referenced Jan 20, 2017
This was referenced Feb 26, 2017
calebamiles
added
the
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
label
Feb 27, 2017
This test has been consistently passing in the past couple of weeks. Should we close it? |
This was referenced Mar 10, 2017
This was referenced Mar 20, 2017
This was referenced Mar 28, 2017
This was referenced Apr 4, 2017
This was referenced Apr 19, 2017
This was referenced Apr 29, 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.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-kops-aws/1705/
Failed: [k8s.io] DisruptionController should update PodDisruptionBudget status {Kubernetes e2e suite}
Previous issues for this test: #34119
The text was updated successfully, but these errors were encountered: