This job view page is being replaced by Spyglass soon. Check out the new job view.
PRnixpanic: Fix a panic for in-tree drivers that partialy support Block volume metrics
Tests 1 failed / 416 succeeded
Started2021-05-19 13:47
Refs 101587

Test Failures

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

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 19 14:06:01.392: Pod became ready in 14.005684995s, 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_18.xml

Filter through log files | View test history on testgrid

Show 416 Passed Tests

Show 5353 Skipped Tests