This job view page is being replaced by Spyglass soon. Check out the new job view.
PRpohly: component-base: move v/vmodule/log-flush-frequency into LoggingConfiguration
Tests 0 failed / 0 succeeded
Started2021-11-04 18:33
Refs 106090

No Test Failures!

Error lines from build-log.txt

... skipping 754 lines ...
Trying to find master named 'e2e-a640af6885-95646-master'
Looking for address 'e2e-a640af6885-95646-master-ip'
Using master: e2e-a640af6885-95646-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 "gce-up-c1-4-glat-up-clu_e2e-a640af6885-95646" set.
User "gce-up-c1-4-glat-up-clu_e2e-a640af6885-95646" set.
Context "gce-up-c1-4-glat-up-clu_e2e-a640af6885-95646" created.
Switched to context "gce-up-c1-4-glat-up-clu_e2e-a640af6885-95646".
... skipping 49 lines ...
e2e-a640af6885-95646-windows-node-group-766j   Ready                      <none>   17s     v1.23.0-alpha.4.96+8488fea8ebf5ce
e2e-a640af6885-95646-windows-node-group-f8xn   Ready                      <none>   29s     v1.23.0-alpha.4.96+8488fea8ebf5ce
e2e-a640af6885-95646-windows-node-group-htcj   Ready                      <none>   18s     v1.23.0-alpha.4.96+8488fea8ebf5ce
Warning: v1 ComponentStatus is deprecated in v1.19+
Validate output:
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE                         ERROR
etcd-1               Healthy   {"health":"true","reason":""}   
etcd-0               Healthy   {"health":"true","reason":""}   
controller-manager   Healthy   ok                              
scheduler            Healthy   ok                              
Cluster validation succeeded
Done, listing cluster services:
... skipping 112 lines ...