This job view page is being replaced by Spyglass soon. Check out the new job view.
PR249043822: Fix:Job didn't delete pods within activeDeadlineSeconds
ResultABORTED
Tests 0 failed / 80 succeeded
Started2022-04-08 00:03
Elapsed57m27s
Revision7031695f32cb68634c6fd5984d15ba14942fa2dd
Refs 97101
job-versionv1.24.0-beta.0.111+1da2ab6c5ccd08
kubetest-version
revisionv1.24.0-beta.0.111+1da2ab6c5ccd08

No Test Failures!


Show 80 Passed Tests

Error lines from build-log.txt

... skipping 717 lines ...
Looking for address 'e2e-97101-95a39-master-ip'
Looking for address 'e2e-97101-95a39-master-internal-ip'
Using master: e2e-97101-95a39-master (external IP: 34.138.50.62; 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-97101-95a39" set.
User "k8s-infra-e2e-boskos-scale-21_e2e-97101-95a39" set.
Context "k8s-infra-e2e-boskos-scale-21_e2e-97101-95a39" created.
Switched to context "k8s-infra-e2e-boskos-scale-21_e2e-97101-95a39".
... skipping 229 lines ...
e2e-97101-95a39-minion-group-zghk   Ready                         <none>   69s    v1.24.0-beta.0.111+1da2ab6c5ccd08
e2e-97101-95a39-minion-group-zs36   Ready                         <none>   67s    v1.24.0-beta.0.111+1da2ab6c5ccd08
e2e-97101-95a39-minion-heapster     Ready                         <none>   91s    v1.24.0-beta.0.111+1da2ab6c5ccd08
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 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.50.62
GLBCDefaultBackend is running at https://34.138.50.62/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://34.138.50.62/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://34.138.50.62/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
... skipping 3015 lines ...