This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 5 failed / 177 succeeded
Started2020-02-14 00:41
Elapsed3h29m
Revision
Buildergke-prow-default-pool-cf4891d4-z214
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/933c0bd1-e0b4-4cf6-8693-edbd4bb9d090/targets/test'}}
poda72c8346-4ec2-11ea-b4dd-def017072732
resultstorehttps://source.cloud.google.com/results/invocations/933c0bd1-e0b4-4cf6-8693-edbd4bb9d090/targets/test
infra-commit989c1a080
job-versionv1.18.0-alpha.5.54+4bb8df4464f440
master_os_imagecos-77-12371-114-0
node_os_imagecos-77-12371-114-0
poda72c8346-4ec2-11ea-b4dd-def017072732
repogithub.com/containerd/cri
repo-commitcf0e0a1e2c864e7115098f7a7624056bc0749df7
repos{u'github.com/containerd/cri': u'master'}
revisionv1.18.0-alpha.5.54+4bb8df4464f440

Test Failures


Kubernetes e2e suite [sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works 1m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-scheduling\]\sSchedulerPreemption\s\[Serial\]\svalidates\sbasic\spreemption\sworks$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:104
Feb 14 03:28:43.902: Unexpected error:
    <*errors.errorString | 0xc000414230>: {
        s: "pod ran to completion",
    }
    pod ran to completion
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:672
				
				Click to see stdout/stderrfrom junit_01.xml

Find ran mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-scheduling] SchedulerPreemption [Serial] validates lower priority pod preemption by critical pod 1m2s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-scheduling\]\sSchedulerPreemption\s\[Serial\]\svalidates\slower\spriority\spod\spreemption\sby\scritical\spod$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:184
Test Panicked
/usr/local/go/src/runtime/panic.go:75

Panic: runtime error: index out of range [0] with length 0

Full stack:
k8s.io/kubernetes/test/e2e/scheduling.glob..func5.4()
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:216 +0xa5e
k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0002f8200)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:111 +0x30a
k8s.io/kubernetes/test/e2e.TestE2E(0xc0002f8200)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:111 +0x2b
testing.tRunner(0xc0002f8200, 0x4cf70b0)
	/usr/local/go/src/testing/testing.go:909 +0xc9
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:960 +0x350
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive] Should test that pv used in a pod that is deleted while the kubelet is down cleans up when the kubelet returns. 1m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\sVolumes\s\[Driver\:\spd\.csi\.storage\.gke\.io\]\[Serial\]\s\[Testpattern\:\sDynamic\sPV\s\(block\svolmode\)\]\sdisruptive\[Disruptive\]\sShould\stest\sthat\spv\sused\sin\sa\spod\sthat\sis\sdeleted\swhile\sthe\skubelet\sis\sdown\scleans\sup\swhen\sthe\skubelet\sreturns\.$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/disruptive.go:150
Feb 14 03:30:49.050: waiting for csi driver node registration on: error waiting for CSI driver pd.csi.storage.gke.io registration on node bootstrap-e2e-minion-group-rs85: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/csi.go:466
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works 6m9s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\sVolumes\s\[Driver\:\spd\.csi\.storage\.gke\.io\]\[Serial\]\s\[Testpattern\:\sDynamic\sPV\s\(default\sfs\)\(allowExpansion\)\]\svolume\-expand\sVerify\sif\soffline\sPVC\sexpansion\sworks$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:163
Feb 14 01:12:06.308: while recreating pod for resizing
Unexpected error:
    <*errors.errorString | 0xc002914c20>: {
        s: "pod \"security-context-18b1375b-3908-4f9f-96d2-48e684520dcd\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-18b1375b-3908-4f9f-96d2-48e684520dcd" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:211
				
				Click to see stdout/stderrfrom junit_01.xml

Find for mentions in log files | View test history on testgrid


Test 3h12m

error during ./hack/ginkgo-e2e.sh --ginkgo.focus=\[Serial\]|\[Disruptive\] --ginkgo.skip=\[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 177 Passed Tests

Show 4677 Skipped Tests