This job view page is being replaced by Spyglass soon. Check out the new job view.
PRcofyc: Prioritizing nodes based on volume capacity
ResultFAILURE
Tests 4 failed / 826 succeeded
Started2021-03-04 04:18
Elapsed1h2m
Revision
Builder9a7ea20e-7ca0-11eb-9364-8238eb26f90b
Refs master:9658145f
96347:441731af
infra-commit2fcf02230
job-versionv1.21.0-beta.0.374+32853c7bf12979
master_os_imageubuntu-2004-focal-v20200423
node_os_imageubuntu-2004-focal-v20200423
repok8s.io/kubernetes
repo-commit32853c7bf129798afe7cb7fa49acdc12a2052b5f
repos{u'k8s.io/kubernetes': u'master:9658145f8acb84b8c8e2179ab7023ed76b1b249b,96347:441731af742f59c5d6652c34da3efdceae115249', u'k8s.io/release': u'master'}
revisionv1.21.0-beta.0.374+32853c7bf12979

Test Failures


Kubernetes e2e suite [sig-apps] CronJob should not emit unexpected warnings 6m49s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sCronJob\sshould\snot\semit\sunexpected\swarnings$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/cronjob.go:206
Mar  4 04:54:02.808: Failed to ensure at least on finished job exists in namespace cronjob-932
Unexpected error:
    <*errors.errorString | 0xc000246240>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/cronjob.go:217
				
				Click to see stdout/stderrfrom junit_23.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should implement legacy replacement when the update strategy is OnDelete 10m2s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sStatefulSet\sBasic\sStatefulSet\sfunctionality\s\[StatefulSetBasic\]\sshould\simplement\slegacy\sreplacement\swhen\sthe\supdate\sstrategy\sis\sOnDelete$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/statefulset.go:501
Mar  4 05:11:03.046: Failed waiting for pods to enter running: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/statefulset/wait.go:80
				
				Click to see stdout/stderrfrom junit_23.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] kubelet [sig-node] Clean up pods on node kubelet should be able to delete 10 pods per node in 1m0s. 5m10s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\skubelet\s\[sig\-node\]\sClean\sup\spods\son\snode\skubelet\sshould\sbe\sable\sto\sdelete\s10\spods\sper\snode\sin\s1m0s\.$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/kubelet.go:341
Mar  4 04:59:12.547: Unexpected error:
    <*errors.errorString | 0xc003552190>: {
        s: "Only 0 pods started out of 30",
    }
    Only 0 pods started out of 30
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/kubelet.go:354
				
				Click to see stdout/stderrfrom junit_23.xml

Filter through log files | View test history on testgrid


Test 25m50s

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

Filter through log files | View test history on testgrid


Show 826 Passed Tests

Show 4914 Skipped Tests