This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 6 failed / 152 succeeded
Started2021-05-26 02:32
Elapsed1h30m
Revision
Builder8ab0180c-bdca-11eb-ac18-ce307f2c917d
infra-commit74f589290
job-versionv1.22.0-alpha.2.165+5078091aa5b82b
kubetest-version
repok8s.io/kubernetes
repo-commit5078091aa5b82bd1de32d209a489645d50713705
repos{u'k8s.io/kubernetes': u'master'}
revisionv1.22.0-alpha.2.165+5078091aa5b82b

Test Failures


E2eNode Suite [sig-node] Pods should run through the lifecycle of Pods and PodStatus [Conformance] 5m0s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sPods\sshould\srun\sthrough\sthe\slifecycle\sof\sPods\sand\sPodStatus\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
failed to see Pod pod-test in namespace pods-3536 running
Unexpected error:
    <*errors.errorString | 0xc00027cc30>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/pods.go:951
				
				Click to see stdout/stderrfrom junit_cos-stable1_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [sig-node] Pods should run through the lifecycle of Pods and PodStatus [Conformance] 5m0s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sPods\sshould\srun\sthrough\sthe\slifecycle\sof\sPods\sand\sPodStatus\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
failed to see Pod pod-test in namespace pods-4231 running
Unexpected error:
    <*errors.errorString | 0xc00027cc30>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/pods.go:951
				
				Click to see stdout/stderrfrom junit_cos-stable2_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [sig-node] Pods should run through the lifecycle of Pods and PodStatus [Conformance] 5m0s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sPods\sshould\srun\sthrough\sthe\slifecycle\sof\sPods\sand\sPodStatus\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
failed to see Pod pod-test in namespace pods-4283 running
Unexpected error:
    <*errors.errorString | 0xc00027ac30>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/pods.go:951
				
				Click to see stdout/stderrfrom junit_ubuntu_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [sig-node] Probing container should be ready immediately after startupProbe succeeds 48s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sProbing\scontainer\sshould\sbe\sready\simmediately\safter\sstartupProbe\ssucceeds$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/container_probe.go:400
May 26 02:42:12.182: Pod became ready in 26.003586905s, 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/local/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
				
				Click to see stdout/stderrfrom junit_cos-stable2_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [sig-node] Probing container should be ready immediately after startupProbe succeeds 1m6s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sProbing\scontainer\sshould\sbe\sready\simmediately\safter\sstartupProbe\ssucceeds$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/container_probe.go:400
May 26 02:42:34.465: Pod became ready in 44.004132632s, 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/local/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
				
				Click to see stdout/stderrfrom junit_cos-stable1_01.xml

Filter through log files | View test history on testgrid


kubetest Node Tests 1h29m

error during go run /go/src/k8s.io/kubernetes/test/e2e_node/runner/remote/run_remote.go --cleanup --logtostderr --vmodule=*=4 --ssh-env=gce --results-dir=/workspace/_artifacts --project=k8s-jkns-gke-ubuntu-serial --zone=us-west1-b --ssh-user=prow --ssh-key=/workspace/.ssh/google_compute_engine --ginkgo-flags=--nodes=1 --skip="\[Flaky\]|\[NodeConformance\]|\[NodeFeature:.+\]|\[NodeSpecialFeature:.+\]|\[NodeAlphaFeature:.+\]|\[Legacy:.+\]|\[Benchmark\]|\[Feature:SCTPConnectivity\]" --test_args=--kubelet-flags="--cgroups-per-qos=true --cgroup-root=/" --test-timeout=5h0m0s --image-config-file=/workspace/test-infra/jobs/e2e_node/image-config.yaml: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 152 Passed Tests

Show 894 Skipped Tests