This job view page is being replaced by Spyglass soon. Check out the new job view.
PRtkashem: apimachinery: add context bound polling
ResultFAILURE
Tests 1 failed / 414 succeeded
Started2021-05-03 14:25
Elapsed28m50s
Revisionc526cf1e3930f3bad3e07afd8936bd76c3ceac58
Refs 101668

Test Failures


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

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
May  3 14:42:38.829: Pod became ready in 24.006197524s, 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_10.xml

Filter through log files | View test history on testgrid


Show 414 Passed Tests

Show 5353 Skipped Tests