This job view page is being replaced by Spyglass soon. Check out the new job view.
PRtedyu: Don't try to create VolumeSpec immediately after underlying PVC is being deleted
ResultFAILURE
Tests 3 failed / 757 succeeded
Started2020-01-14 03:51
Elapsed53m4s
Revision
Buildergke-prow-default-pool-cf4891d4-s6x6
Refs master:61d36e4a
86670:70e0f7c1
pod046d3512-3681-11ea-8690-5a63508ef2b8
infra-commitac4bda6bc
job-versionv1.18.0-alpha.1.660+4c8a2520149b8d
master_os_imagecos-77-12371-89-0
node_os_imagecos-77-12371-89-0
pod046d3512-3681-11ea-8690-5a63508ef2b8
repok8s.io/kubernetes
repo-commit4c8a2520149b8d7b8bc999bce2d9e1c1af8ea2ff
repos{u'k8s.io/kubernetes': u'master:61d36e4a43b831f960b190b81d371cb33b5f20d1,86670:70e0f7c1a9063000ec543087fe91405e2a1b151c', u'k8s.io/release': u'master'}
revisionv1.18.0-alpha.1.660+4c8a2520149b8d

Test Failures


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: dir-link] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2 2m28s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sdir\-link\]\sTwo\spods\smounting\sa\slocal\svolume\sat\sthe\ssame\stime\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
test/e2e/storage/persistent_volumes-local.go:244
Jan 14 04:15:01.867: Unexpected error:
    <*errors.errorString | 0xc002978240>: {
        s: "pod \"security-context-7865558c-1b0e-4586-ba32-dadc50d04fd6\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-7865558c-1b0e-4586-ba32-dadc50d04fd6" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:710
				
				Click to see stdout/stderrfrom junit_06.xml

Find security-context-7865558c-1b0e-4586-ba32-dadc50d04fd6 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: tmpfs] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2 2m42s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\stmpfs\]\sTwo\spods\smounting\sa\slocal\svolume\sone\safter\sthe\sother\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
test/e2e/storage/persistent_volumes-local.go:250
Jan 14 04:08:52.198: Unexpected error:
    <*errors.errorString | 0xc001c1f3f0>: {
        s: "pod \"security-context-e6ee6659-27ca-42b6-ace0-2fbb39b1bcac\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-e6ee6659-27ca-42b6-ace0-2fbb39b1bcac" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:747
				
				Click to see stdout/stderrfrom junit_03.xml

Find security-context-e6ee6659-27ca-42b6-ace0-2fbb39b1bcac mentions in log files | View test history on testgrid


Test 30m41s

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

Show 4099 Skipped Tests