This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 8 failed / 217 succeeded
Started2019-08-20 23:44
Elapsed1h29m
Revisionmaster
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/a2505cf6-ce1d-48a0-ac86-3db2f460a115/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/a2505cf6-ce1d-48a0-ac86-3db2f460a115/targets/test
job-versionv1.17.0-alpha.0.345+8cf05f514c139b
master_os_imagecos-73-11647-163-0
node_os_imagecos-73-11647-163-0
revisionv1.17.0-alpha.0.345+8cf05f514c139b

Test Failures


1h2m

error during /home/prow/go/src/k8s.io/gce-k8s-windows-testing/run-e2e.sh --ginkgo.focus=\[Conformance\]|\[NodeConformance\]|\[sig-windows\] --ginkgo.skip=\[LinuxOnly\]|\[Serial\] --minStartupPods=8 --node-os-distro=windows: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] Burst scaling should run to completion even with unhealthy pods [Slow] [Conformance] 12m44s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sStatefulSet\s\[k8s\.io\]\sBasic\sStatefulSet\sfunctionality\s\[StatefulSetBasic\]\sBurst\sscaling\sshould\srun\sto\scompletion\seven\swith\sunhealthy\spods\s\[Slow\]\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:699
Aug 21 00:44:54.023: Failed waiting for stateful set status.readyReplicas updated to 0: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/statefulset/wait.go:247
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-cli] Kubectl client [k8s.io] Guestbook application should create and stop a working application [Conformance] 11m30s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\s\[k8s\.io\]\sGuestbook\sapplication\sshould\screate\sand\sstop\sa\sworking\sapplication\s\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:699
Aug 21 00:39:34.113: Frontend service did not start serving content in 600 seconds.
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:2149
				
				Click to see stdout/stderrfrom junit_05.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should be able to create a functioning NodePort service [Conformance] 3m11s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sbe\sable\sto\screate\sa\sfunctioning\sNodePort\sservice\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:699
Service is not reachable within 2m0s timeout on endpoint nodeport-test:80 over TCP protocol
Unexpected error:
    <*errors.errorString | 0xc0000d3050>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/service/jig.go:822
				
				Click to see stdout/stderrfrom junit_06.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: gcepd] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath should support creating multiple subpath from same volumes [Slow] 6m40s

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\(ntfs\)\]\[sig\-windows\]\ssubPath\sshould\ssupport\screating\smultiple\ssubpath\sfrom\ssame\svolumes\s\[Slow\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:277
Unexpected error:
    <*errors.errorString | 0xc0024e1ae0>: {
        s: "expected pod \"pod-subpath-test-gcepd-dynamicpv-zm86\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-gcepd-dynamicpv-zm86\" to be \"success or failure\"",
    }
    expected pod "pod-subpath-test-gcepd-dynamicpv-zm86" success: Gave up after waiting 5m0s for pod "pod-subpath-test-gcepd-dynamicpv-zm86" to be "success or failure"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:1679
				
				Click to see stdout/stderrfrom junit_03.xml

Find pod-subpath-test-gcepd-dynamicpv-zm86 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: gcepd] [Testpattern: Inline-volume (ntfs)][sig-windows] volumes should allow exec of files on the volume 5m46s

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\:\sInline\-volume\s\(ntfs\)\]\[sig\-windows\]\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:186
Unexpected error:
    <*errors.errorString | 0xc0037a3c00>: {
        s: "expected pod \"exec-volume-test-gcepd-s4g5\" success: Gave up after waiting 5m0s for pod \"exec-volume-test-gcepd-s4g5\" to be \"success or failure\"",
    }
    expected pod "exec-volume-test-gcepd-s4g5" success: Gave up after waiting 5m0s for pod "exec-volume-test-gcepd-s4g5" to be "success or failure"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:1679
				
				Click to see stdout/stderrfrom junit_04.xml

Find exec-volume-test-gcepd-s4g5 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Projected secret optional updates should be reflected in volume [NodeConformance] [Conformance] 10m22s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sProjected\ssecret\soptional\supdates\sshould\sbe\sreflected\sin\svolume\s\[NodeConformance\]\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:153
Aug 21 01:00:35.929: Couldn't delete ns: "projected-3532": namespace projected-3532 was not deleted with limit: timed out waiting for the condition, pods remaining: 1 (&errors.errorString{s:"namespace projected-3532 was not deleted with limit: timed out waiting for the condition, pods remaining: 1"})
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:337
				
				Click to see stdout/stderrfrom junit_06.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-windows] Services should be able to create a functioning NodePort service for Windows 2m17s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-windows\]\sServices\sshould\sbe\sable\sto\screate\sa\sfunctioning\sNodePort\sservice\sfor\sWindows$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/windows/service.go:42
Aug 21 00:22:14.130: Failed waiting for pods to be running: timeout waiting for 1 pods to be ready
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/service/jig.go:682
				
				Click to see stdout/stderrfrom junit_08.xml

Filter through log files | View test history on testgrid


Show 217 Passed Tests

Show 4625 Skipped Tests