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
e2e failure: "Deployment deployment should scale up and down in the right order" is flaky #15369
Labels
area/test
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Comments
wojtek-t
added
area/test
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
labels
Oct 9, 2015
Link to an example run where this happened? (Want to see the logs) |
dchen1107
added a commit
that referenced
this issue
Oct 12, 2015
…ployment-test Label flaky deployment test as per #15369.
RichieEscarez
pushed a commit
to RichieEscarez/kubernetes
that referenced
this issue
Dec 4, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/test
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
I've seen few failure like this today:
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/deployment.go:40
Expected
: 1
to equal
: 2
cc @nikhiljindal
The text was updated successfully, but these errors were encountered: