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.

Sign up for GitHub

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

Jump to bottom

kubernetes-e2e-gci-gke-updown: broken test run #34193

Closed
k8s-github-robot opened this issue Oct 6, 2016 · 10 comments
Closed

kubernetes-e2e-gci-gke-updown: broken test run #34193

k8s-github-robot opened this issue Oct 6, 2016 · 10 comments
Assignees
@rmmh
Labels
area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@k8s-github-robot
Copy link

Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-updown/-1/

Run so broken it didn't make JUnit output!
@k8s-github-robot 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. area/test-infra labels Oct 6, 2016
@k8s-github-robot
Copy link
Author

Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-updown/1663/

Run so broken it didn't make JUnit output!

@k8s-github-robot
Copy link
Author

Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-updown/2239/

Run so broken it didn't make JUnit output!

@k8s-github-robot k8s-github-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Oct 10, 2016
@k8s-github-robot
Copy link
Author

Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-updown/2240/

Run so broken it didn't make JUnit output!

@k8s-github-robot k8s-github-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Oct 10, 2016
@k8s-github-robot
Copy link
Author

Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-updown/2241/

Run so broken it didn't make JUnit output!

@k8s-github-robot
Copy link
Author

Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-updown/2323/

Run so broken it didn't make JUnit output!

@k8s-github-robot
Copy link
Author

Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-updown/2529/

Run so broken it didn't make JUnit output!

@rmmh
Copy link
Contributor

rmmh commented Oct 12, 2016

dupe of #34446

@rmmh rmmh closed this as completed Oct 12, 2016
@zmerlynn
Copy link
Member

@rmmh: Why? This looks like it succeeded in log-dump.sh, and isn't the kubemark provider, which was the last issue left. So at least 2529 is unrelated to #34446?

@zmerlynn zmerlynn reopened this Oct 12, 2016
@rmmh
Copy link
Contributor

rmmh commented Oct 12, 2016

Ok, dupe of #34446 AND #28188. I don't know why the bot is claiming these runs don't have JUnit output, many of them do.

@rmmh rmmh closed this as completed Oct 12, 2016
@wojtek-t
Copy link
Member

I confirm that this is fixed now.
@zmerlynn - thanks a lot for fixing this!

@k8s-github-robot k8s-github-robot mentioned this issue Oct 21, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rmmh rmmh

Labels
area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rmmh @zmerlynn @wojtek-t @k8s-github-robot