This job view page is being replaced by Spyglass soon. Check out the new job view.
PRadrianreber: Minimal checkpointing support
ResultABORTED
Tests 0 failed / 80 succeeded
Started2022-07-12 06:39
Elapsed1h5m
Revisiondf149a8145e22619c660d418e79f4d5281e66191
Refs 104907
job-versionv1.25.0-alpha.2.209+925c3251ff1f45
kubetest-version
revisionv1.25.0-alpha.2.209+925c3251ff1f45

No Test Failures!


Show 80 Passed Tests

Error lines from build-log.txt

... skipping 718 lines ...
Looking for address 'e2e-104907-95a39-master-ip'
Looking for address 'e2e-104907-95a39-master-internal-ip'
Using master: e2e-104907-95a39-master (external IP: 34.138.151.223; 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-17_e2e-104907-95a39" set.
User "k8s-infra-e2e-boskos-scale-17_e2e-104907-95a39" set.
Context "k8s-infra-e2e-boskos-scale-17_e2e-104907-95a39" created.
Switched to context "k8s-infra-e2e-boskos-scale-17_e2e-104907-95a39".
... skipping 228 lines ...
e2e-104907-95a39-minion-group-zlk2   Ready                         <none>   62s   v1.25.0-alpha.2.209+925c3251ff1f45
e2e-104907-95a39-minion-group-zxnn   Ready                         <none>   61s   v1.25.0-alpha.2.209+925c3251ff1f45
e2e-104907-95a39-minion-heapster     Ready                         <none>   75s   v1.25.0-alpha.2.209+925c3251ff1f45
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":""}   
scheduler            Healthy   ok                              
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.138.151.223
GLBCDefaultBackend is running at https://34.138.151.223/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://34.138.151.223/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://34.138.151.223/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
... skipping 3015 lines ...
Specify --start=60681 in the next get-serial-port-output invocation to get only the new output starting from here.
scp: /var/log/cluster-autoscaler.log*: No such file or directory
scp: /var/log/fluentd.log*: No such file or directory
scp: /var/log/kubelet.cov*: No such file or directory
scp: /var/log/cl2-**: No such file or directory
scp: /var/log/startupscript.log*: No such file or directory
ERROR: (gcloud.compute.scp) [/usr/bin/scp] exited with return code [1].
Dumping logs from nodes to GCS directly at 'gs://sig-scalability-logs/pull-kubernetes-e2e-gce-100-performance/1546745028292907008' using logexporter
namespace/logexporter created
secret/google-service-account created
daemonset.apps/logexporter created
Listing marker files (gs://sig-scalability-logs/pull-kubernetes-e2e-gce-100-performance/1546745028292907008/logexported-nodes-registry) for successful nodes...
CommandException: One or more URLs matched no objects.
... skipping 385 lines ...