This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjoelsmith: Fix log spam for du failure on pod etc-hosts metrics
ResultFAILURE
Tests 1 failed / 414 succeeded
Started2021-05-04 15:48
Elapsed28m3s
Revision1e0ca5bdc7cb24a9c8cf8ab09f6715e4224ad4c0
Refs 101708

Test Failures


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

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  4 16:11:55.848: Pod became ready in 6.007090807s, 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_16.xml

Filter through log files | View test history on testgrid


Show 414 Passed Tests

Show 5353 Skipped Tests