This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 2 failed / 65 succeeded
Started2020-02-18 05:29
Elapsed1h4m
Revision
Buildergke-prow-default-pool-cf4891d4-w60c
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/3aef1065-3a47-4b84-a658-cedd23af50be/targets/test'}}
pod896f310b-520f-11ea-9bea-16a0f55e352c
resultstorehttps://source.cloud.google.com/results/invocations/3aef1065-3a47-4b84-a658-cedd23af50be/targets/test
infra-commit92e4176fa
pod896f310b-520f-11ea-9bea-16a0f55e352c
reposigs.k8s.io/gcp-compute-persistent-disk-csi-driver
repo-commita38158ba5ac0a51952bf5d3742ca7a8fef355cb4
repos{u'sigs.k8s.io/gcp-compute-persistent-disk-csi-driver': u'master'}

Test Failures


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: gcepd] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works 6m50s

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\(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 18 06:21:12.034: while recreating pod for resizing
Unexpected error:
    <*errors.errorString | 0xc003482b60>: {
        s: "pod \"security-context-97ae84f2-0f25-4442-aad6-38ee1cbaf389\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-97ae84f2-0f25-4442-aad6-38ee1cbaf389" 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_20.xml

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


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: gcepd] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node 6m10s

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\(filesystem\svolmode\)\]\smultiVolume\s\[Slow\]\sshould\saccess\sto\stwo\svolumes\swith\sthe\ssame\svolume\smode\sand\sretain\sdata\sacross\spod\srecreation\son\sthe\ssame\snode$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:131
Feb 18 06:22:17.246: Unexpected error:
    <*errors.errorString | 0xc002728a60>: {
        s: "pod \"security-context-c3c9b109-0784-49dc-ac7b-0f21b9b8fcae\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-c3c9b109-0784-49dc-ac7b-0f21b9b8fcae" 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/multivolume.go:383
				
				Click to see stdout/stderrfrom junit_23.xml

Find security-context-c3c9b109-0784-49dc-ac7b-0f21b9b8fcae mentions in log files | View test history on testgrid


Show 65 Passed Tests

Show 4778 Skipped Tests