-
Notifications
You must be signed in to change notification settings - Fork 39.6k
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] Pods should *not* be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite} #29614
Labels
kind/flake
Categorizes issue or PR as related to a flaky test.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Comments
k8s-github-robot
added
priority/backlog
Higher priority than priority/awaiting-more-evidence.
kind/flake
Categorizes issue or PR as related to a flaky test.
labels
Jul 26, 2016
This was referenced Aug 23, 2016
[FLAKE-PING] @cjcullen This flaky-test issue would love to have more attention... |
[FLAKE-PING] @cjcullen This flaky-test issue would love to have more attention. |
2 similar comments
[FLAKE-PING] @cjcullen This flaky-test issue would love to have more attention. |
[FLAKE-PING] @cjcullen This flaky-test issue would love to have more attention. |
GKE test stack's flakiness. |
This was referenced Dec 22, 2016
This was referenced Jan 7, 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/logs/kubernetes-e2e-gke/11976/
Failed: [k8s.io] Pods should not be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite}
The text was updated successfully, but these errors were encountered: