kubernetes-pull-build-test-e2e-gce: broken test run #29222
Labels
area/test-infra
kind/flake
Categorizes issue or PR as related to a flaky test.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/27911/kubernetes-pull-build-test-e2e-gce/49655/
Multiple broken tests:
Failed: [k8s.io] Downward API should provide default limits.cpu/memory from node capacity {Kubernetes e2e suite}
Issues about this test specifically: #28065
Failed: [k8s.io] Port forwarding [k8s.io] With a server that expects a client request should support a client that connects, sends data, and disconnects [Conformance] {Kubernetes e2e suite}
Issues about this test specifically: #27680
Failed: [k8s.io] Networking should function for intra-pod communication [Conformance] {Kubernetes e2e suite}
Issues about this test specifically: #26960 #27235
Failed: [k8s.io] Pods should not be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite}
The text was updated successfully, but these errors were encountered: