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
Tests 1 failed / 414 succeeded
Started2021-05-04 16:24
Refs 101708

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$'
May  4 16:42:47.295: Pod became ready in 20.010747261s, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.
				Click to see stdout/stderrfrom junit_14.xml

Filter through log files | View test history on testgrid

Show 414 Passed Tests

Show 5353 Skipped Tests