This job view page is being replaced by Spyglass soon. Check out the new job view.
PRwojtek-t: [WIP] Pf remove goroutine
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-07-29 15:57
Elapsed45m49s
Revision27f3ec0424378bb2b02bf42c4fc0a5fa67c73720
Refs 104010

No Test Failures!


Error lines from build-log.txt

... skipping 682 lines ...
Looking for address 'e2e-104010-95a39-master-ip'
Looking for address 'e2e-104010-95a39-master-internal-ip'
Using master: e2e-104010-95a39-master (external IP: 34.139.143.82; 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-21_e2e-104010-95a39" set.
User "k8s-infra-e2e-boskos-scale-21_e2e-104010-95a39" set.
Context "k8s-infra-e2e-boskos-scale-21_e2e-104010-95a39" created.
Switched to context "k8s-infra-e2e-boskos-scale-21_e2e-104010-95a39".
... skipping 228 lines ...
e2e-104010-95a39-minion-group-zn1k   Ready                         <none>   50s   v1.23.0-alpha.0.46+069af5266279b2
e2e-104010-95a39-minion-group-zsl4   Ready                         <none>   51s   v1.23.0-alpha.0.46+069af5266279b2
e2e-104010-95a39-minion-group-zwhd   Ready                         <none>   50s   v1.23.0-alpha.0.46+069af5266279b2
Warning: v1 ComponentStatus is deprecated in v1.19+
Validate output:
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE                         ERROR
scheduler            Healthy   ok                              
etcd-1               Healthy   {"health":"true","reason":""}   
etcd-0               Healthy   {"health":"true","reason":""}   
controller-manager   Healthy   ok                              
Cluster validation encountered some problems, but cluster should be in working order
...ignoring non-fatal errors in validate-cluster
Done, listing cluster services:

Kubernetes control plane is running at https://34.139.143.82
GLBCDefaultBackend is running at https://34.139.143.82/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://34.139.143.82/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://34.139.143.82/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
... skipping 348 lines ...
I0729 16:27:38.607298  105509 util.go:85] Not enough active targets (0), expected at least (3), waiting for more to become active...
I0729 16:27:38.808415  105509 util.go:85] Not enough active targets (0), expected at least (6), waiting for more to become active...
I0729 16:27:53.609001  105509 util.go:85] Not enough active targets (0), expected at least (3), waiting for more to become active...
I0729 16:27:53.812517  105509 util.go:85] Not enough active targets (0), expected at least (6), waiting for more to become active...
I0729 16:28:08.608502  105509 util.go:85] Not enough active targets (0), expected at least (3), waiting for more to become active...
I0729 16:28:08.810227  105509 util.go:85] Not enough active targets (0), expected at least (6), waiting for more to become active...
E0729 16:28:08.904357  105509 etcd_metrics.go:147] EtcdMetrics: failed to collect etcd database size
I0729 16:28:23.612992  105509 util.go:93] 1/3 targets are ready, example not ready target: {map[container:dns endpoint:metrics instance:10.64.79.3:8080 job:dns namespace:probes pod:dns-854b7dccbf-shmbb service:dns] unknown}
I0729 16:28:23.812795  105509 util.go:93] 2/6 targets are ready, example not ready target: {map[container:ping-server endpoint:metrics instance:10.64.89.3:8080 job:ping-server namespace:probes pod:ping-server-596b77b4cb-5nbcx service:ping-server] unknown}
{"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-07-29T16:28:25Z"}
++ early_exit_handler
++ '[' -n 186 ']'
++ kill -TERM 186
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 4 lines ...