This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 2 failed / 859 succeeded
Started2021-05-04 02:08
Elapsed37m16s
Revision
Builder90a0e3dd-ac7d-11eb-9596-661b35ad9ad2
infra-commitee6348061
job-versionv1.22.0-alpha.1.129+31030820be979e
kubetest-version
master_os_imagecos-85-13310-1041-9
node_os_imagecos-85-13310-1041-9
revisionv1.22.0-alpha.1.129+31030820be979e

Test Failures


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

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$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/container_probe.go:400
May  4 02:27:54.924: Pod became ready in 8.481786229s, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
				
				Click to see stdout/stderrfrom junit_04.xml

Filter through log files | View test history on testgrid


kubetest Test 21m12s

error during ./hack/ginkgo-e2e.sh --ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true --cluster-ip-range=10.64.0.0/14: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 859 Passed Tests

Show 4925 Skipped Tests