This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-03-31 06:32
Elapsed2h0m
Revisionwindows-gce-poc
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/235c316b-c24d-492a-9246-cea3de53d4b9/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/235c316b-c24d-492a-9246-cea3de53d4b9/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 148 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/k8s.io/kubernetes'
2020/03/31 06:35:14 process.go:155: Step 'make -C /home/prow/go/src/k8s.io/kubernetes bazel-release' finished in 2m29.692972994s
2020/03/31 06:35:14 util.go:265: Flushing memory.
2020/03/31 06:35:40 util.go:275: flushMem error (page cache): exit status 1
2020/03/31 06:35:40 process.go:153: Running: /home/prow/go/src/k8s.io/release/push-build.sh --nomock --verbose --noupdatelatest --bucket=kubernetes-release-dev --ci --gcs-suffix=/ci-kubernetes-e2e-windows-gce-poc --allow-dup
push-build.sh: BEGIN main on 0e9fe37d-7319-11ea-8574-7e2b78ec67cb Tue Mar 31 06:35:40 UTC 2020


push-build.sh is running a *REAL* push!!

... skipping 841 lines ...
Trying to find master named 'e2e-0b8951f1dd-be9ce-master'
Looking for address 'e2e-0b8951f1dd-be9ce-master-ip'
Using master: e2e-0b8951f1dd-be9ce-master (external IP: 34.83.128.2; 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 "gce-up-glat-up-etcd_e2e-0b8951f1dd-be9ce" set.
User "gce-up-glat-up-etcd_e2e-0b8951f1dd-be9ce" set.
Context "gce-up-glat-up-etcd_e2e-0b8951f1dd-be9ce" created.
Switched to context "gce-up-glat-up-etcd_e2e-0b8951f1dd-be9ce".
... skipping 40 lines ...
e2e-0b8951f1dd-be9ce-minion-group-b6r1         Ready                      <none>   5m5s    v1.13.0-alpha.0.19390+bb51d829e180d8
e2e-0b8951f1dd-be9ce-minion-group-jr6p         Ready                      <none>   5m3s    v1.13.0-alpha.0.19390+bb51d829e180d8
e2e-0b8951f1dd-be9ce-windows-node-group-kp47   Ready                      <none>   14s     v1.17.2
e2e-0b8951f1dd-be9ce-windows-node-group-ml8p   Ready                      <none>   12s     v1.17.2
e2e-0b8951f1dd-be9ce-windows-node-group-thxm   Ready                      <none>   5s      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 107 lines ...
++ cd /home/prow/go/src/k8s.io/windows-testing/gce
++ pwd
+ SCRIPT_ROOT=/home/prow/go/src/k8s.io/windows-testing/gce
+ kubectl create -f /home/prow/go/src/k8s.io/windows-testing/gce/prepull-head.yaml
daemonset.apps/prepull-test-containers created
+ kubectl wait --for=condition=ready pod -l prepull-test-images=e2e --timeout 30m
{"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-31T08:32:40Z"}
2020/03/31 08:32:42 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/31 08:32:42 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 1h43m31.689706198s
2020/03/31 08:32:42 e2e.go:534: Dumping logs locally to: /logs/artifacts
2020/03/31 08:32:42 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: gce-up-glat-up-etcd
Zone: us-west1-b
Dumping logs from master locally to '/logs/artifacts'
Trying to find master named 'e2e-0b8951f1dd-be9ce-master'
Looking for address 'e2e-0b8951f1dd-be9ce-master-ip'
Using master: e2e-0b8951f1dd-be9ce-master (external IP: 34.83.128.2; internal IP: (not set))
{"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-31T08:32:55Z"}