This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-03-29 15:24
Elapsed2h0m
Revisionmaster
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/7f9d4b53-5d51-41b6-8406-f93d10cd4bba/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/7f9d4b53-5d51-41b6-8406-f93d10cd4bba/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 343 lines ...
Trying to find master named 'e2e-f1a617c583-b49e0-master'
Looking for address 'e2e-f1a617c583-b49e0-master-ip'
Using master: e2e-f1a617c583-b49e0-master (external IP: 35.230.20.37)
Waiting up to 300 seconds for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This may time out if there was some uncaught error during start up.

..............Kubernetes cluster created.
Cluster "k8s-jkns-gci-gce-ingress1-4_e2e-f1a617c583-b49e0" set.
User "k8s-jkns-gci-gce-ingress1-4_e2e-f1a617c583-b49e0" set.
Context "k8s-jkns-gci-gce-ingress1-4_e2e-f1a617c583-b49e0" created.
Switched to context "k8s-jkns-gci-gce-ingress1-4_e2e-f1a617c583-b49e0".
... skipping 36 lines ...
e2e-f1a617c583-b49e0-minion-group-f1kp         Ready                      <none>   3m49s   v1.15.12-beta.0.9+8de4013f5815f7
e2e-f1a617c583-b49e0-minion-group-gbdl         Ready                      <none>   3m50s   v1.15.12-beta.0.9+8de4013f5815f7
e2e-f1a617c583-b49e0-windows-node-group-10v2   Ready                      <none>   10s     v1.15.12-beta.0.9+8de4013f5815f7
e2e-f1a617c583-b49e0-windows-node-group-2jgm   Ready                      <none>   10s     v1.15.12-beta.0.9+8de4013f5815f7
e2e-f1a617c583-b49e0-windows-node-group-h9p0   Ready                      <none>   9s      v1.15.12-beta.0.9+8de4013f5815f7
Validate output:
NAME                 STATUS    MESSAGE             ERROR
etcd-1               Healthy   {"health":"true"}   
etcd-0               Healthy   {"health":"true"}   
scheduler            Healthy   ok                  
controller-manager   Healthy   ok                  
Cluster validation succeeded
Done, listing cluster services:
... skipping 119 lines ...
prepull-test-containers-5vdgg   25/31   Running   29         102m   10.64.1.3   e2e-f1a617c583-b49e0-windows-node-group-2jgm   <none>           <none>
prepull-test-containers-95mxs   23/31   Running   30         102m   10.64.3.3   e2e-f1a617c583-b49e0-windows-node-group-10v2   <none>           <none>
prepull-test-containers-hpjgh   25/31   Running   28         102m   10.64.2.3   e2e-f1a617c583-b49e0-windows-node-group-h9p0   <none>           <none>
+ kubectl delete -f /home/prow/go/src/k8s.io/windows-testing/gce/prepull-1.15.yaml
daemonset.apps "prepull-test-containers" deleted
+ kubectl wait --for=delete pod -l prepull-test-images=e2e --timeout 3m
{"component":"entrypoint","file":"prow/entrypoint/run.go:164","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 2h0m0s timeout","time":"2020-03-29T17:24:06Z"}
2020/03/29 17:24:07 process.go:199: Interrupt after 2h0m0s timeout during /home/prow/go/src/k8s.io/windows-testing/gce/run-e2e.sh --ginkgo.focus=\[Conformance\]|\[NodeConformance\]|\[sig-windows\] --ginkgo.skip=\[LinuxOnly\]|\[Serial\]|\[Feature:.+\] --minStartupPods=8 --node-os-distro=windows. Will terminate in another 15m
2020/03/29 17:24:07 process.go:155: Step '/home/prow/go/src/k8s.io/windows-testing/gce/run-e2e.sh --ginkgo.focus=\[Conformance\]|\[NodeConformance\]|\[sig-windows\] --ginkgo.skip=\[LinuxOnly\]|\[Serial\]|\[Feature:.+\] --minStartupPods=8 --node-os-distro=windows' finished in 1h50m26.737749645s
2020/03/29 17:24:07 e2e.go:534: Dumping logs locally to: /logs/artifacts
2020/03/29 17:24:07 process.go:153: Running: ./cluster/log-dump/log-dump.sh /logs/artifacts
Checking for custom logdump instances, if any
Sourcing kube-util.sh
... skipping 2 lines ...
Network Project: k8s-jkns-gci-gce-ingress1-4
Zone: us-west1-b
Dumping logs from master locally to '/logs/artifacts'
Trying to find master named 'e2e-f1a617c583-b49e0-master'
Looking for address 'e2e-f1a617c583-b49e0-master-ip'
Using master: e2e-f1a617c583-b49e0-master (external IP: 35.230.20.37)
{"component":"entrypoint","file":"prow/entrypoint/run.go:245","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Process did not exit before 15s grace period","time":"2020-03-29T17:24:21Z"}