This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 3 failed / 192 succeeded
Started2020-02-15 07:26
Elapsed4h21m
Revision
Buildergke-prow-default-pool-cf4891d4-rtv5
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/9ab1013d-1040-411f-96d8-1ecc1423a022/targets/test'}}
pod6384bf6e-4fc4-11ea-9bea-16a0f55e352c
resultstorehttps://source.cloud.google.com/results/invocations/9ab1013d-1040-411f-96d8-1ecc1423a022/targets/test
infra-commitf5dd3ee0e
job-versionv1.17.4-beta.0.1+aa9a28326e8075
master_os_imagecos-77-12371-89-0
node_os_imagecos-77-12371-89-0
pod6384bf6e-4fc4-11ea-9bea-16a0f55e352c
revisionv1.17.4-beta.0.1+aa9a28326e8075

Test Failures


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property 1m2s

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\)\]\svolume\-expand\sshould\snot\sallow\sexpansion\sof\spvcs\swithout\sAllowVolumeExpansion\sproperty$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:144
Feb 15 09:42:41.035: waiting for csi driver node registration on: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/drivers/csi.go:452
				
				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 at the same time should be able to write from pod1 and read from pod2 6.94s

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\sat\sthe\ssame\stime\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
Feb 15 10:17:48.170: Unexpected error:
    <*errors.errorString | 0xc0003e62c0>: {
        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 4h4m

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

Show 4666 Skipped Tests