This job view page is being replaced by Spyglass soon. Check out the new job view.
Tests 0 failed / 0 succeeded
Started2020-03-30 18:07
links{u'resultstore': {u'url': u''}}

No Test Failures!

Error lines from build-log.txt

... skipping 147 lines ...
INFO: 4483 processes: 4462 remote cache hit, 21 processwrapper-sandbox.
INFO: Build completed successfully, 4548 total actions
INFO: Build completed successfully, 4548 total actions
make: Leaving directory '/home/prow/go/src/'
2020/03/30 18:10:32 process.go:155: Step 'make -C /home/prow/go/src/ bazel-release' finished in 2m20.340555481s
2020/03/30 18:10:32 util.go:265: Flushing memory.
2020/03/30 18:11:05 util.go:275: flushMem error (page cache): exit status 1
2020/03/30 18:11:05 process.go:153: Running: /home/prow/go/src/ --nomock --verbose --noupdatelatest --bucket=kubernetes-release-dev --ci --gcs-suffix=/ci-kubernetes-e2e-windows-gce-poc --allow-dup BEGIN main on fab402dc-72b0-11ea-8574-7e2b78ec67cb Mon Mar 30 18:11:05 UTC 2020 is running a *REAL* push!!

... skipping 841 lines ...
Trying to find master named 'e2e-8c707ea5f9-be9ce-master'
Looking for address 'e2e-8c707ea5f9-be9ce-master-ip'
Using master: e2e-8c707ea5f9-be9ce-master (external IP:; internal IP: (not set))
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-gce-serial-1-3_e2e-8c707ea5f9-be9ce" set.
User "k8s-jkns-gce-serial-1-3_e2e-8c707ea5f9-be9ce" set.
Context "k8s-jkns-gce-serial-1-3_e2e-8c707ea5f9-be9ce" created.
Switched to context "k8s-jkns-gce-serial-1-3_e2e-8c707ea5f9-be9ce".
... skipping 40 lines ...
e2e-8c707ea5f9-be9ce-minion-group-fg0v         Ready                      <none>   5m19s   v1.13.0-alpha.0.19390+bb51d829e180d8
e2e-8c707ea5f9-be9ce-minion-group-hfnr         Ready                      <none>   5m24s   v1.13.0-alpha.0.19390+bb51d829e180d8
e2e-8c707ea5f9-be9ce-windows-node-group-jznb   Ready                      <none>   41s     v1.17.2
e2e-8c707ea5f9-be9ce-windows-node-group-pb3s   Ready                      <none>   10s     v1.17.2
e2e-8c707ea5f9-be9ce-windows-node-group-xfkc   Ready                      <none>   40s     v1.17.2
Validate output:
NAME                 STATUS    MESSAGE             ERROR
controller-manager   Healthy   ok                  
etcd-1               Healthy   {"health":"true"}   
scheduler            Healthy   ok                  
etcd-0               Healthy   {"health":"true"}   
Cluster validation succeeded
Done, listing cluster services:
... skipping 120 lines ...
prepull-test-containers-vmcwr   14/17   CrashLoopBackOff   87         100m   e2e-8c707ea5f9-be9ce-windows-node-group-jznb   <none>           <none>
+ kubectl delete -f /home/prow/go/src/
daemonset.apps "prepull-test-containers" deleted
+ kubectl wait --for=delete pod -l prepull-test-images=e2e --timeout 3m
pod/prepull-test-containers-4zqw7 condition met
pod/prepull-test-containers-fm6lw condition met
{"component":"entrypoint","file":"prow/entrypoint/run.go:164","func":"","level":"error","msg":"Process did not finish before 2h0m0s timeout","time":"2020-03-30T20:08:07Z"}
2020/03/30 20:08:09 process.go:199: Interrupt after 2h0m0s timeout during /home/prow/go/src/ --ginkgo.focus=\[Conformance\]|\[NodeConformance\]|\[sig-windows\] --ginkgo.skip=\[LinuxOnly\]|\[Serial\]|\[Feature:.+\] --minStartupPods=8 --node-os-distro=windows. Will terminate in another 15m
2020/03/30 20:08:09 process.go:155: Step '/home/prow/go/src/ --ginkgo.focus=\[Conformance\]|\[NodeConformance\]|\[sig-windows\] --ginkgo.skip=\[LinuxOnly\]|\[Serial\]|\[Feature:.+\] --minStartupPods=8 --node-os-distro=windows' finished in 1h43m16.942272347s
2020/03/30 20:08:09 e2e.go:534: Dumping logs locally to: /logs/artifacts
2020/03/30 20:08:09 process.go:153: Running: ./cluster/log-dump/ /logs/artifacts
Checking for custom logdump instances, if any
... skipping 2 lines ...
Network Project: k8s-jkns-gce-serial-1-3
Zone: us-west1-b
Dumping logs from master locally to '/logs/artifacts'
Trying to find master named 'e2e-8c707ea5f9-be9ce-master'
Looking for address 'e2e-8c707ea5f9-be9ce-master-ip'
Using master: e2e-8c707ea5f9-be9ce-master (external IP:; internal IP: (not set))
{"component":"entrypoint","file":"prow/entrypoint/run.go:245","func":"","level":"error","msg":"Process did not exit before 15s grace period","time":"2020-03-30T20:08:23Z"}