This job view page is being replaced by Spyglass soon. Check out the new job view.
PRmm4tt: Kubemark: allow choosing image-service
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-04-16 10:55
Elapsed41m36s
Revisione79053bdad8882dabf40ac893fe60a215ebec32c
Refs 101145

No Test Failures!


Error lines from build-log.txt

... skipping 673 lines ...
Looking for address 'e2e-101145-ac87c-master-ip'
Looking for address 'e2e-101145-ac87c-master-internal-ip'
Using master: e2e-101145-ac87c-master (external IP: 35.227.43.111; internal IP: 10.40.0.2)
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-infra-e2e-boskos-scale-15_e2e-101145-ac87c" set.
User "k8s-infra-e2e-boskos-scale-15_e2e-101145-ac87c" set.
Context "k8s-infra-e2e-boskos-scale-15_e2e-101145-ac87c" created.
Switched to context "k8s-infra-e2e-boskos-scale-15_e2e-101145-ac87c".
... skipping 29 lines ...
e2e-101145-ac87c-minion-group-fb46   Ready                      <none>   13s   v1.22.0-alpha.0.433+528a6f0b271de9
e2e-101145-ac87c-minion-group-hmbt   Ready                      <none>   14s   v1.22.0-alpha.0.433+528a6f0b271de9
e2e-101145-ac87c-minion-group-w78w   Ready                      <none>   14s   v1.22.0-alpha.0.433+528a6f0b271de9
Warning: v1 ComponentStatus is deprecated in v1.19+
Validate output:
Warning: v1 ComponentStatus is deprecated in v1.19+
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 224 lines ...
Looking for address 'e2e-101145-ac87c-kubemark-master-ip'
Looking for address 'e2e-101145-ac87c-kubemark-master-internal-ip'
Using master: e2e-101145-ac87c-kubemark-master (external IP: 34.74.140.130; internal IP: 10.40.0.11)
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-infra-e2e-boskos-scale-15_e2e-101145-ac87c-kubemark" set.
User "k8s-infra-e2e-boskos-scale-15_e2e-101145-ac87c-kubemark" set.
Context "k8s-infra-e2e-boskos-scale-15_e2e-101145-ac87c-kubemark" created.
Switched to context "k8s-infra-e2e-boskos-scale-15_e2e-101145-ac87c-kubemark".
... skipping 21 lines ...
Found 1 node(s).
NAME                               STATUS                     ROLES    AGE   VERSION
e2e-101145-ac87c-kubemark-master   Ready,SchedulingDisabled   <none>   5s    v1.22.0-alpha.0.433+528a6f0b271de9
Warning: v1 ComponentStatus is deprecated in v1.19+
Validate output:
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE             ERROR
controller-manager   Healthy   ok                  
scheduler            Healthy   ok                  
etcd-1               Healthy   {"health":"true"}   
etcd-0               Healthy   {"health":"true"}   
Cluster validation succeeded
Done, listing cluster services:
... skipping 7698 lines ...
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
Cleaning up after docker
++ docker ps -aq
++ xargs -r docker rm -f
{"component":"entrypoint","file":"prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2021-04-16T11:37:27Z"}