-
Notifications
You must be signed in to change notification settings - Fork 39k
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
kubernetes-e2e-gci-gke-staging-parallel: broken test run #35289
Comments
Run so broken it didn't make JUnit output! |
Run so broken it didn't make JUnit output! |
Run so broken it didn't make JUnit output! |
Looks like a get-kube.sh flake?
|
ugh, it's the curl problem all over again - not just limited to downloading from GitHub, apparently. kinda weird how the download got stuck for 8s or so. |
Run so broken it didn't make JUnit output! |
Run so broken it didn't make JUnit output! |
Run so broken it didn't make JUnit output! |
1733: timeout |
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-staging-parallel/1353/
Multiple broken tests:
Failed: [k8s.io] Networking [k8s.io] Granular Checks should function for pod communication between nodes {Kubernetes e2e suite}
Issues about this test specifically: #30131 #31402
Failed: [k8s.io] ResourceQuota should create a ResourceQuota and capture the life of a service. {Kubernetes e2e suite}
Issues about this test specifically: #29040
Failed: [k8s.io] Pods should support remote command execution over websockets {Kubernetes e2e suite}
Failed: [k8s.io] Services should be able to up and down services {Kubernetes e2e suite}
Issues about this test specifically: #26128 #26685 #33408
Previous issues for this suite: #33415 #34192 #34773
The text was updated successfully, but these errors were encountered: