-
Notifications
You must be signed in to change notification settings - Fork 40.7k
Automated cherry pick of #17973 #17984
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
Automated cherry pick of #17973 #17984
Conversation
Labelling this PR as size/M |
GCE e2e build/test failed for commit 4becda5. |
@k8s-bot test this please |
GCE e2e build/test failed for commit 4becda5. |
@k8s-bot test this |
GCE e2e build/test failed for commit 4becda5. |
@k8s-bot test this |
GCE e2e build/test failed for commit 4becda5. |
@k8s-bot test this |
GCE e2e build/test failed for commit 4becda5. |
It looks like a second flake to me - reruning tests. |
GCE e2e build/test failed for commit 4becda5. |
@liggitt - tests are reliably failing, can you investigate? It still looks unrelated to me...
|
with no changes on my side, failures have ranged from 2-6, most with non-overlapping failures:
the same change passes fine in master and 1.1. not sure what to do with this. none of the failures look related to my pull (which hard-fails attempts to create or get logs or exec/attach to pods with invalid node names, which wouldn't have worked anyway) |
@fabianofranz is seeing similar inconsistent non-overlapping flakes on his release-1.0 pull #17954 |
@k8s-bot test this |
GCE e2e test build/test passed for commit 4becda5. |
aaaaaaand got a clean run :-) :-/ |
@brendandburns clean test runs against release-1.0 branch, which is showing flaky e2e tests... I would recommend merging this |
manual merge... lifespan of maintaining the 1.0 branch is diminishing anyway... |
…3-upstream-release-1.0 Automated cherry pick of #17973
Cherry pick of #17973 on release-1.0.