This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 691 succeeded
Started2021-09-15 09:36
Elapsed34m1s
Revisionrelease-1.21

Test Failures


Kubernetes e2e suite [sig-node] Probing container should be ready immediately after startupProbe succeeds 1m20s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sProbing\scontainer\sshould\sbe\sready\simmediately\safter\sstartupProbe\ssucceeds$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/container_probe.go:400
Sep 15 09:51:25.391: Pod became ready in 38.00836312s, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
				
				Click to see stdout/stderrfrom junit_19.xml

Filter through log files | View test history on testgrid


Show 691 Passed Tests

Show 5078 Skipped Tests