This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 691 succeeded
Started2022-07-29 14:25
Elapsed36m31s
Revisionrelease-1.21

Test Failures


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

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
Jul 29 14:58:02.223: Pod became ready in 8.04839007s, 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_12.xml

Filter through log files


Show 691 Passed Tests

Show 5081 Skipped Tests