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 04:15
Elapsed2h0m
Revisionmaster
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/861c0aec-44e2-4168-8953-f05a2a946d8a/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/861c0aec-44e2-4168-8953-f05a2a946d8a/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 354 lines ...
Trying to find master named 'e2e-eaaef37631-6c91a-master'
Looking for address 'e2e-eaaef37631-6c91a-master-ip'
Using master: e2e-eaaef37631-6c91a-master (external IP: 34.83.1.127; 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 "kubernetes-gci-scale_e2e-eaaef37631-6c91a" set.
User "kubernetes-gci-scale_e2e-eaaef37631-6c91a" set.
Context "kubernetes-gci-scale_e2e-eaaef37631-6c91a" created.
Switched to context "kubernetes-gci-scale_e2e-eaaef37631-6c91a".
... skipping 39 lines ...
e2e-eaaef37631-6c91a-minion-group-p7jt         Ready                      <none>   4m36s   v1.17.5-beta.0.22+ea3eeb494a528e
e2e-eaaef37631-6c91a-minion-group-qjcx         Ready                      <none>   4m34s   v1.17.5-beta.0.22+ea3eeb494a528e
e2e-eaaef37631-6c91a-windows-node-group-3zvn   Ready                      <none>   23s     v1.17.5-beta.0.22+ea3eeb494a528e
e2e-eaaef37631-6c91a-windows-node-group-frf0   Ready                      <none>   13s     v1.17.5-beta.0.22+ea3eeb494a528e
e2e-eaaef37631-6c91a-windows-node-group-h0h7   Ready                      <none>   27s     v1.17.5-beta.0.22+ea3eeb494a528e
Validate output:
NAME                 STATUS    MESSAGE             ERROR
etcd-1               Healthy   {"health":"true"}   
scheduler            Healthy   ok                  
controller-manager   Healthy   ok                  
etcd-0               Healthy   {"health":"true"}   
Cluster validation succeeded
Done, listing cluster services:
... skipping 314 lines ...
      cmd.exe
      /c
      ping -n 1800 127.0.0.1 >NUL
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Tue, 31 Mar 2020 06:07:38 +0000
      Finished:     Tue, 31 Mar 2020 06:07:39 +0000
    Ready:          False
    Restart Count:  21
    Requests:
... skipping 237 lines ...
                 node.kubernetes.io/pid-pressure:NoSchedule
                 node.kubernetes.io/unreachable:NoExecute
                 node.kubernetes.io/unschedulable:NoSchedule
Events:
  Type     Reason   Age                   From                                                   Message
  ----     ------   ----                  ----                                                   -------
  Warning  BackOff  9m6s (x372 over 89m)  kubelet, e2e-eaaef37631-6c91a-windows-node-group-h0h7  Back-off restarting failed container
  Normal   Pulled   3m33s (x42 over 91m)  kubelet, e2e-eaaef37631-6c91a-windows-node-group-h0h7  (combined from similar events): Container image "e2eteam/busybox:1.29" already present on machine


Name:         prepull-test-containers-s8s6m
Namespace:    default
Priority:     0
... skipping 188 lines ...
      cmd.exe
      /c
      ping -n 1800 127.0.0.1 >NUL
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Tue, 31 Mar 2020 06:12:57 +0000
      Finished:     Tue, 31 Mar 2020 06:12:58 +0000
    Ready:          False
    Restart Count:  22
    Requests:
... skipping 237 lines ...
                 node.kubernetes.io/pid-pressure:NoSchedule
                 node.kubernetes.io/unreachable:NoExecute
                 node.kubernetes.io/unschedulable:NoSchedule
Events:
  Type     Reason   Age                    From                                                   Message
  ----     ------   ----                   ----                                                   -------
  Warning  BackOff  8m54s (x377 over 89m)  kubelet, e2e-eaaef37631-6c91a-windows-node-group-3zvn  Back-off restarting failed container
  Normal   Pulled   3m53s (x48 over 91m)   kubelet, e2e-eaaef37631-6c91a-windows-node-group-3zvn  (combined from similar events): Container image "e2eteam/etcd:3.4.3" already present on machine


Name:         prepull-test-containers-wpjgd
Namespace:    default
Priority:     0
... skipping 188 lines ...
      cmd.exe
      /c
      ping -n 1800 127.0.0.1 >NUL
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Tue, 31 Mar 2020 06:09:25 +0000
      Finished:     Tue, 31 Mar 2020 06:09:26 +0000
    Ready:          False
    Restart Count:  21
    Requests:
... skipping 239 lines ...
                 node.kubernetes.io/unreachable:NoExecute
                 node.kubernetes.io/unschedulable:NoSchedule
Events:
  Type     Reason   Age                    From                                                   Message
  ----     ------   ----                   ----                                                   -------
  Normal   Pulled   33m (x28 over 91m)     kubelet, e2e-eaaef37631-6c91a-windows-node-group-frf0  (combined from similar events): Container image "e2eteam/echoserver:2.2" already present on machine
  Warning  BackOff  3m31s (x320 over 88m)  kubelet, e2e-eaaef37631-6c91a-windows-node-group-frf0  Back-off restarting failed container
+ kubectl delete -f /home/prow/go/src/k8s.io/windows-testing/gce/prepull-1.17.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-31T06:15:37Z"}
2020/03/31 06:15:40 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 06:15:40 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 1h49m11.415386801s
2020/03/31 06:15:40 e2e.go:534: Dumping logs locally to: /logs/artifacts
2020/03/31 06:15:40 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: kubernetes-gci-scale
Zone: us-west1-b
Dumping logs from master locally to '/logs/artifacts'
Trying to find master named 'e2e-eaaef37631-6c91a-master'
Looking for address 'e2e-eaaef37631-6c91a-master-ip'
Using master: e2e-eaaef37631-6c91a-master (external IP: 34.83.1.127; 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-31T06:15:52Z"}