Skip to content
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

Closed
wojtek-t opened this issue Oct 9, 2015 · 5 comments
Assignees
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
Copy link
Member

wojtek-t commented Oct 9, 2015

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

@wojtek-t 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
@nikhiljindal
Copy link
Contributor

Link to an example run where this happened? (Want to see the logs)

@liggitt
Copy link
Member

liggitt commented Oct 10, 2015

#15224 (comment)

@dchen1107
Copy link
Member

@nikhiljindal
Copy link
Contributor

#15508 marked the test as flaky so it should not be blocking PR merges anymore.
#15572 attempts to fix the flake.

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.
Projects
None yet
Development

No branches or pull requests

5 participants