This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 4 failed / 972 succeeded
Started2020-04-17 12:01
Elapsed3h16m
Revision
Buildergke-scalability-build-cpu16-disk1000-d2de3eff-c07c
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/4a345d2c-2f99-448f-8176-88065715948d/targets/test'}}
pod1f765395-80a3-11ea-a39b-b29f9a0538b7
resultstorehttps://source.cloud.google.com/results/invocations/4a345d2c-2f99-448f-8176-88065715948d/targets/test
infra-commit13d4a722f
job-versionv1.19.0-alpha.1.653+d24b9286297147
master_os_imagecos-81-12871-59-0
node_os_imagecos-81-12871-59-0
pod1f765395-80a3-11ea-a39b-b29f9a0538b7
revisionv1.19.0-alpha.1.653+d24b9286297147

Test Failures


Kubernetes e2e suite [sig-storage] Dynamic Provisioning DynamicProvisioner [Slow] should test that deleting a claim before the volume is provisioned deletes the volume. 6m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sDynamic\sProvisioning\sDynamicProvisioner\s\[Slow\]\sshould\stest\sthat\sdeleting\sa\sclaim\sbefore\sthe\svolume\sis\sprovisioned\sdeletes\sthe\svolume\.$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/volume_provisioning.go:481
Apr 17 12:59:14.789: PersistentVolumes were not deleted as expected. 1 remain
Unexpected error:
    <*errors.errorString | 0xc0104b1470>: {
        s: "Error waiting for PVs to be deleted: timed out waiting for the condition",
    }
    Error waiting for PVs to be deleted: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/volume_provisioning.go:521
				
				Click to see stdout/stderrfrom junit_12.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)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node 6m2s

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\)\]\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
Apr 17 12:41:46.683: Unexpected error:
    <*errors.errorString | 0xc0129c9e20>: {
        s: "pod \"security-context-c3a4ed2b-f32c-4603-bce1-3ae41ab3e271\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-c3a4ed2b-f32c-4603-bce1-3ae41ab3e271" 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:387
				
				Click to see stdout/stderrfrom junit_33.xml

Find security-context-c3a4ed2b-f32c-4603-bce1-3ae41ab3e271 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 different node 5m59s

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\sdifferent\snode$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:161
Apr 17 12:44:17.978: Unexpected error:
    <*errors.errorString | 0xc002a9fee0>: {
        s: "pod \"security-context-9c8d66f6-75e9-4e36-bd5e-8c3d59e8fa79\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-9c8d66f6-75e9-4e36-bd5e-8c3d59e8fa79" 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:387
				
				Click to see stdout/stderrfrom junit_06.xml

Find security-context-9c8d66f6-75e9-4e36-bd5e-8c3d59e8fa79 mentions in log files | View test history on testgrid


Test 2h3m

error during ./hack/ginkgo-e2e.sh --ginkgo.skip=\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[DisabledForLargeClusters\] --minStartupPods=8 --node-schedulable-timeout=90m --logexporter-gcs-path=gs://kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-correctness/1251118525695660033/artifacts --report-dir=/workspace/_artifacts --disable-log-dump=true --cluster-ip-range=10.64.0.0/11: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 972 Passed Tests

Show 4046 Skipped Tests