This job view page is being replaced by Spyglass soon. Check out the new job view.
PRmortent: Promote PodDisruptionBudget to policy/v1
ResultFAILURE
Tests 1 failed / 672 succeeded
Started2021-03-09 06:03
Elapsed35m17s
Revision7254baf54111380d6f1deb9889edfd1e3aa4c629
Refs 99290

Test Failures


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

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:376
Mar  9 06:21:34.679: Pod became ready in 8.015233288s, 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_06.xml

Filter through log files | View test history on testgrid


Show 672 Passed Tests

Show 5064 Skipped Tests