This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjiahuif: Remove Bazel from cloud-provider-gcp
Tests 0 failed / 0 succeeded
Started2021-10-01 21:14
Refs 259

No Test Failures!

Error lines from build-log.txt

... skipping 311 lines ...
Trying to find master named 'kt2-9590c26d-22fc-master'
Looking for address 'kt2-9590c26d-22fc-master-ip'
Using master: kt2-9590c26d-22fc-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-gce-1-5_kt2-9590c26d-22fc" set.
User "k8s-gce-1-5_kt2-9590c26d-22fc" set.
Context "k8s-gce-1-5_kt2-9590c26d-22fc" created.
Switched to context "k8s-gce-1-5_kt2-9590c26d-22fc".
... skipping 24 lines ...
kt2-9590c26d-22fc-minion-group-369h   Ready                      <none>   31s   v1.22.0
kt2-9590c26d-22fc-minion-group-hgqm   Ready                      <none>   32s   v1.22.0
kt2-9590c26d-22fc-minion-group-xhq1   Ready                      <none>   33s   v1.22.0
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 succeeded
Done, listing cluster services:
... skipping 38 lines ...