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 21:47
Elapsed3h35m
Revision
Buildergke-prow-default-pool-cf4891d4-8gg3
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/9e65069a-cbeb-46cc-b4d0-2aeefd0f2740/targets/test'}}
pod819f304d-4f73-11ea-9bea-16a0f55e352c
resultstorehttps://source.cloud.google.com/results/invocations/9e65069a-cbeb-46cc-b4d0-2aeefd0f2740/targets/test
infra-commit46626dea0
job-versionv1.18.0-alpha.5.133+b290e0b7ab292b
master_os_imagecos-77-12371-175-0
node_os_imagecos-77-12371-175-0
pod819f304d-4f73-11ea-9bea-16a0f55e352c
repogithub.com/containerd/cri
repo-commitcf0e0a1e2c864e7115098f7a7624056bc0749df7
repos{u'github.com/containerd/cri': u'master'}
revisionv1.18.0-alpha.5.133+b290e0b7ab292b

Test Failures


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

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 23:51:06.661: Unexpected error:
    <*errors.errorString | 0xc00042c110>: {
        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(0xc000c28200)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:111 +0x30a
k8s.io/kubernetes/test/e2e.TestE2E(0xc000c28200)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:111 +0x2b
testing.tRunner(0xc000c28200, 0x4cf9ac8)
	/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)(allowExpansion)] volume-expand Verify if offline PVC expansion works 6m1s

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\)\(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 15 00:59:51.108: while recreating pod for resizing
Unexpected error:
    <*errors.errorString | 0xc0030724f0>: {
        s: "pod \"security-context-de50373a-546a-476d-ad1b-8424969fdb67\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-de50373a-546a-476d-ad1b-8424969fdb67" 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


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node 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\)\]\smultiVolume\s\[Slow\]\sshould\saccess\sto\stwo\svolumes\swith\sthe\ssame\svolume\smode\sand\sretain\sdata\sacross\spod\srecreation\son\sdifferent\snode$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:161
Feb 15 00:37:47.526: waiting for csi driver node registration on: error waiting for CSI driver pd.csi.storage.gke.io registration on node bootstrap-e2e-minion-group-4d0b: 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


Test 3h14m

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 4678 Skipped Tests