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
ResultFAILURE
Tests 2 failed / 413 succeeded
Started2021-05-04 07:48
Elapsed31m32s
Revisionac1bb3e1de4062f9e726a841bc44c165aa1b87a5
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\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/network/kube_proxy.go:52
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
/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_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$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/container_probe.go:400
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.
/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_19.xml

Filter through log files | View test history on testgrid


Show 413 Passed Tests

Show 5353 Skipped Tests