This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 5 failed / 187 succeeded
Started2020-01-10 11:43
Elapsed4h32m
Revision
Buildergke-prow-default-pool-cf4891d4-0mh6
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/62d697b0-9583-41de-9512-6187ea3fd7ef/targets/test'}}
pod50b7bf87-339e-11ea-a4dc-8213d962824c
resultstorehttps://source.cloud.google.com/results/invocations/62d697b0-9583-41de-9512-6187ea3fd7ef/targets/test
infra-commit1856252e3
job-versionv1.17.1-beta.0.50+27d95a9cae6bb1
master_os_imagecos-77-12371-89-0
node_os_imageubuntu-gke-1804-d1809-0-v20200110
pod50b7bf87-339e-11ea-a4dc-8213d962824c
revisionv1.17.1-beta.0.50+27d95a9cae6bb1

Test Failures


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] volumes should allow exec of files on the volume 5m28s

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\(xfs\)\]\[Slow\]\svolumes\sshould\sallow\sexec\sof\sfiles\son\sthe\svolume$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:191
Jan 10 13:09:37.336: Unexpected error:
    <*errors.errorString | 0xc003246950>: {
        s: "expected pod \"exec-volume-test-pd-csi-storage-gke-io-dynamicpv-4rqr\" success: Gave up after waiting 5m0s for pod \"exec-volume-test-pd-csi-storage-gke-io-dynamicpv-4rqr\" to be \"success or failure\"",
    }
    expected pod "exec-volume-test-pd-csi-storage-gke-io-dynamicpv-4rqr" success: Gave up after waiting 5m0s for pod "exec-volume-test-pd-csi-storage-gke-io-dynamicpv-4rqr" to be "success or failure"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:894
				
				Click to see stdout/stderrfrom junit_01.xml

Find exec-volume-test-pd-csi-storage-gke-io-dynamicpv-4rqr 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 (xfs)][Slow] volumes should store data 10m5s

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\(xfs\)\]\[Slow\]\svolumes\sshould\sstore\sdata$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:150
Jan 10 14:21:39.903: Failed to create injector pod: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:597
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: gcepd] [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. 1m9s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sgcepd\]\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:149
Jan 10 12:33:31.385: Expected grep stdout to be empty.
Expected
    <string>: pvc-b94d7784-dc3d-4c65-9fec-7479d65cc74c
    
to be empty
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/utils.go:408
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: gce-localssd-scsi-fs] [Serial] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2 1.81s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sgce\-localssd\-scsi\-fs\]\s\[Serial\]\sTwo\spods\smounting\sa\slocal\svolume\sone\safter\sthe\sother\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:189
Jan 10 11:56:01.259: Unexpected error:
    <*errors.errorString | 0xc00059a240>: {
        s: "pod ran to completion",
    }
    pod ran to completion
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/host_exec.go:103
				
				Click to see stdout/stderrfrom junit_01.xml

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


Test 4h15m

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 187 Passed Tests

Show 4664 Skipped Tests