This job view page is being replaced by Spyglass soon. Check out the new job view.
PRAbirdcfly: Automated cherry pick of #110652: fix: --chunk-size with selector returns missing result
ResultABORTED
Tests 0 failed / 0 succeeded
Started2022-06-23 01:30
Elapsed40m27s
Revision7078b8834d8248d3a3207ee34a4a04abda5b3b00
Refs 110735

No Test Failures!


Error lines from build-log.txt

... skipping 718 lines ...
Looking for address 'e2e-110735-95a39-master-ip'
Looking for address 'e2e-110735-95a39-master-internal-ip'
Using master: e2e-110735-95a39-master (external IP: 34.138.189.203; 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-05_e2e-110735-95a39" set.
User "k8s-infra-e2e-boskos-scale-05_e2e-110735-95a39" set.
Context "k8s-infra-e2e-boskos-scale-05_e2e-110735-95a39" created.
Switched to context "k8s-infra-e2e-boskos-scale-05_e2e-110735-95a39".
... skipping 228 lines ...
e2e-110735-95a39-minion-group-wvdf   Ready                         <none>   60s   v1.24.3-rc.0.3+20b3834ad10105
e2e-110735-95a39-minion-group-z2m3   Ready                         <none>   56s   v1.24.3-rc.0.3+20b3834ad10105
e2e-110735-95a39-minion-heapster     Ready                         <none>   73s   v1.24.3-rc.0.3+20b3834ad10105
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":""}   
controller-manager   Healthy   ok                              
etcd-0               Healthy   {"health":"true","reason":""}   
scheduler            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.138.189.203
GLBCDefaultBackend is running at https://34.138.189.203/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://34.138.189.203/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://34.138.189.203/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
... skipping 400 lines ...