-
Notifications
You must be signed in to change notification settings - Fork 40k
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] [HPA] Horizontal pod autoscaling (scale resource: CPU) [k8s.io] [Serial] [Slow] ReplicaSet Should scale from 1 pod to 3 pods and from 3 to 5 {Kubernetes e2e suite} #27917
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
Jun 23, 2016
This was referenced Sep 7, 2016
This was referenced Sep 26, 2016
This was referenced Oct 11, 2016
This was referenced Oct 20, 2016
This was referenced Nov 23, 2016
This was referenced Jan 4, 2017
This was referenced Jan 12, 2017
This was referenced Jan 20, 2017
This was referenced Jan 29, 2017
This was referenced Mar 8, 2017
This was referenced Mar 19, 2017
This was referenced Apr 3, 2017
This was referenced Apr 11, 2017
This was referenced Apr 22, 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-gce-serial/1549/
Failed: [k8s.io] [HPA] Horizontal pod autoscaling (scale resource: CPU) [k8s.io] [Serial] [Slow] ReplicaSet Should scale from 1 pod to 3 pods and from 3 to 5 {Kubernetes e2e suite}
Previous issues for this test: #27397
The text was updated successfully, but these errors were encountered: