This job view page is being replaced by Spyglass soon. Check out the new job view.
PRsaschagrunert: Partly remove support for seccomp annotations
ResultABORTED
Tests 0 failed / 80 succeeded
Started2022-07-19 07:16
Elapsed1h0m
Revision9abe0fddba5e4f87eb257a006370e9b4689229cc
Refs 109819
job-versionv1.25.0-alpha.2.385+4e8d42de31641b
kubetest-version
revisionv1.25.0-alpha.2.385+4e8d42de31641b

No Test Failures!


Show 80 Passed Tests

Error lines from build-log.txt

... skipping 718 lines ...
Looking for address 'e2e-109819-95a39-master-ip'
Looking for address 'e2e-109819-95a39-master-internal-ip'
Using master: e2e-109819-95a39-master (external IP: 34.73.121.222; 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-07_e2e-109819-95a39" set.
User "k8s-infra-e2e-boskos-scale-07_e2e-109819-95a39" set.
Context "k8s-infra-e2e-boskos-scale-07_e2e-109819-95a39" created.
Switched to context "k8s-infra-e2e-boskos-scale-07_e2e-109819-95a39".
... skipping 227 lines ...
e2e-109819-95a39-minion-group-zz56   Ready                         <none>   59s   v1.25.0-alpha.2.385+4e8d42de31641b
e2e-109819-95a39-minion-group-zzl5   Ready                         <none>   61s   v1.25.0-alpha.2.385+4e8d42de31641b
e2e-109819-95a39-minion-heapster     Ready                         <none>   72s   v1.25.0-alpha.2.385+4e8d42de31641b
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":""}   
scheduler            Healthy   ok                              
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.73.121.222
GLBCDefaultBackend is running at https://34.73.121.222/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://34.73.121.222/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://34.73.121.222/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
... skipping 3023 lines ...