This job view page is being replaced by Spyglass soon. Check out the new job view.
PRdims: [WIP][IGNORE ME] dummy-commit-to-test-serial-containerd-job
ResultFAILURE
Tests 1 failed / 706 succeeded
Started2021-07-29 20:27
Elapsed35m41s
Revisione8d8bc55494493c94ad8a8c008fe874bd7221572
Refs 104016

Test Failures


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

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:406
Jul 29 20:48:18.707: Pod became ready in 6.006044409s, 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_13.xml

Filter through log files | View test history on testgrid


Show 706 Passed Tests

Show 5965 Skipped Tests