This job view page is being replaced by Spyglass soon. Check out the new job view.
PRingvagabund: Inject pkg/apis/core/v1 ResourceName helpers through ResourceNameQualifier from cmd/kube-scheduler
Tests 2 failed / 413 succeeded
Started2021-05-04 07:48
Refs 101489

Test Failures

Kubernetes e2e suite [sig-network] KubeProxy should set TCP CLOSE_WAIT timeout [Privileged] 5m42s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sKubeProxy\sshould\sset\sTCP\sCLOSE\_WAIT\stimeout\s\[Privileged\]$'
May  4 08:16:44.852: no valid conntrack entry for port 11302 on node fc00:f853:ccd:e793::3: timed out waiting for the condition
				Click to see stdout/stderrfrom junit_11.xml

Filter through log files | View test history on testgrid

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

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 08:06:37.748: Pod became ready in 14.006575032s, 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_19.xml

Filter through log files | View test history on testgrid

Show 413 Passed Tests

Show 5353 Skipped Tests