This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-05-19 17:02
Elapsed1h34m
Revision
Buildergke-scalability-build-cpu16-disk1000-d2de3eff-w3sm
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/82feab6f-66a1-45c6-ba7b-90201148c6dd/targets/test'}}
pod7328b619-99f2-11ea-aa9b-c69591b579a5
resultstorehttps://source.cloud.google.com/results/invocations/82feab6f-66a1-45c6-ba7b-90201148c6dd/targets/test
infra-commitd13d3ca2a
job-versionv1.19.0-beta.0.1+6c9aab2b098d92
pod7328b619-99f2-11ea-aa9b-c69591b579a5
repok8s.io/kubernetes
repo-commit6c9aab2b098d92adfeba76a4f542cac900393dd1
repos{u'k8s.io/kubernetes': u'master', u'k8s.io/perf-tests': u'master'}
revisionv1.19.0-beta.0.1+6c9aab2b098d92

Test Failures


Up 41m45s

error during ./hack/e2e-internal/e2e-up.sh: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

... skipping 604 lines ...
W0519 17:16:58.444] Trying to find master named 'gce-scale-cluster-master'
W0519 17:16:58.444] Looking for address 'gce-scale-cluster-master-ip'
W0519 17:16:59.286] Looking for address 'gce-scale-cluster-master-internal-ip'
I0519 17:17:00.078] Waiting up to 300 seconds for cluster initialization.
I0519 17:17:00.078] 
I0519 17:17:00.078]   This will continually check to see if the API for kubernetes is reachable.
I0519 17:17:00.078]   This may time out if there was some uncaught error during start up.
I0519 17:17:00.078] 
W0519 17:17:00.179] Using master: gce-scale-cluster-master (external IP: 35.227.6.186; internal IP: 10.40.0.2)
I0519 17:17:00.405] Kubernetes cluster created.
I0519 17:17:00.546] Cluster "kubernetes-scale_gce-scale-cluster" set.
I0519 17:17:00.682] User "kubernetes-scale_gce-scale-cluster" set.
I0519 17:17:00.818] Context "kubernetes-scale_gce-scale-cluster" created.
... skipping 1792 lines ...
W0519 17:47:30.632] scp: /var/log/cluster-autoscaler.log*: No such file or directory
W0519 17:47:30.702] scp: /var/log/konnectivity-server.log*: No such file or directory
W0519 17:47:30.702] scp: /var/log/fluentd.log*: No such file or directory
W0519 17:47:30.702] scp: /var/log/kubelet.cov*: No such file or directory
W0519 17:47:30.703] scp: /var/log/cl2-**: No such file or directory
W0519 17:47:30.703] scp: /var/log/startupscript.log*: No such file or directory
W0519 17:47:30.706] ERROR: (gcloud.compute.scp) [/usr/bin/scp] exited with return code [1].
I0519 17:47:30.807] Dumping logs from nodes to GCS directly at 'gs://kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-performance/1262790701058363395/artifacts' using logexporter
I0519 17:47:30.807] Detecting nodes in the cluster
I0519 17:47:42.903] namespace/logexporter created
I0519 17:47:42.940] secret/google-service-account created
I0519 17:47:42.978] daemonset.apps/logexporter created
I0519 17:47:42.987] Listing marker files (gs://kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-performance/1262790701058363395/artifacts/logexported-nodes-registry) for successful nodes...
... skipping 2549 lines ...
I0519 18:18:44.896] Logexporter didn't succeed on node gce-scale-cluster-minion-group-zd4p. Queuing it for logdump through SSH.
I0519 18:18:44.896] Logexporter didn't succeed on node gce-scale-cluster-minion-group-zdf5. Queuing it for logdump through SSH.
I0519 18:18:44.896] Logexporter didn't succeed on node gce-scale-cluster-minion-group-zjkz. Queuing it for logdump through SSH.
I0519 18:18:44.896] Logexporter didn't succeed on node gce-scale-cluster-minion-group-zjlv. Queuing it for logdump through SSH.
I0519 18:18:44.897] Logexporter didn't succeed on node gce-scale-cluster-minion-group-zm2n. Queuing it for logdump through SSH.
I0519 18:18:44.897] Shutting down test cluster in background.
W0519 18:18:44.997] ./cluster/log-dump/log-dump.sh: line 583: echo: write error: Resource temporarily unavailable
W0519 18:18:44.997] 2020/05/19 18:18:44 process.go:155: Step './cluster/log-dump/log-dump.sh /workspace/_artifacts gs://kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-performance/1262790701058363395/artifacts' finished in 32m16.592070579s
W0519 18:18:44.997] 2020/05/19 18:18:44 process.go:153: Running: ./hack/e2e-internal/e2e-down.sh
W0519 18:18:44.998] Project: kubernetes-scale
W0519 18:18:44.998] Network Project: kubernetes-scale
W0519 18:18:44.998] Zone: us-east1-b
I0519 18:18:46.752] Bringing down cluster using provider: gce
... skipping 50 lines ...
I0519 18:36:00.860] Property "users.kubernetes-scale_gce-scale-cluster-basic-auth" unset.
I0519 18:36:00.996] Property "contexts.kubernetes-scale_gce-scale-cluster" unset.
I0519 18:36:01.000] Cleared config for kubernetes-scale_gce-scale-cluster from /workspace/.kube/config
I0519 18:36:01.000] Done
W0519 18:36:01.011] 2020/05/19 18:36:01 process.go:155: Step './hack/e2e-internal/e2e-down.sh' finished in 17m16.179650993s
W0519 18:36:01.012] 2020/05/19 18:36:01 process.go:96: Saved XML output to /workspace/_artifacts/junit_runner.xml.
W0519 18:36:01.012] 2020/05/19 18:36:01 main.go:312: Something went wrong: starting e2e cluster: error during ./hack/e2e-internal/e2e-up.sh: exit status 1
W0519 18:36:01.012] Traceback (most recent call last):
W0519 18:36:01.012]   File "/workspace/./test-infra/jenkins/../scenarios/kubernetes_e2e.py", line 720, in <module>
W0519 18:36:01.012]     main(parse_args())
W0519 18:36:01.012]   File "/workspace/./test-infra/jenkins/../scenarios/kubernetes_e2e.py", line 570, in main
W0519 18:36:01.012]     mode.start(runner_args)
W0519 18:36:01.013]   File "/workspace/./test-infra/jenkins/../scenarios/kubernetes_e2e.py", line 228, in start
W0519 18:36:01.013]     check_env(env, self.command, *args)
W0519 18:36:01.013]   File "/workspace/./test-infra/jenkins/../scenarios/kubernetes_e2e.py", line 111, in check_env
W0519 18:36:01.013]     subprocess.check_call(cmd, env=env)
W0519 18:36:01.013]   File "/usr/lib/python2.7/subprocess.py", line 190, in check_call
W0519 18:36:01.013]     raise CalledProcessError(retcode, cmd)
W0519 18:36:01.014] subprocess.CalledProcessError: Command '('kubetest', '--dump=/workspace/_artifacts', '--gcp-service-account=/etc/service-account/service-account.json', '--up', '--down', '--provider=gce', '--cluster=gce-scale-cluster', '--gcp-network=gce-scale-cluster', '--extract=ci/latest', '--gcp-nodes=5000', '--gcp-project=kubernetes-scale', '--gcp-zone=us-east1-b', '--test-cmd=/go/src/k8s.io/perf-tests/run-e2e.sh', '--test-cmd-args=cluster-loader2', '--test-cmd-args=--experimental-gcp-snapshot-prometheus-disk=true', '--test-cmd-args=--experimental-prometheus-disk-snapshot-name=ci-kubernetes-e2e-gce-scale-performance-1262790701058363395', '--test-cmd-args=--nodes=5000', '--test-cmd-args=--provider=gce', '--test-cmd-args=--report-dir=/workspace/_artifacts', '--test-cmd-args=--testconfig=testing/density/config.yaml', '--test-cmd-args=--testconfig=testing/load/config.yaml', '--test-cmd-args=--testconfig=testing/access-tokens/config.yaml', '--test-cmd-args=--testoverrides=./testing/density/5000_nodes/override.yaml', '--test-cmd-args=--testoverrides=./testing/experiments/enable_prometheus_api_responsiveness.yaml', '--test-cmd-args=--testoverrides=./testing/experiments/enable_restart_count_check.yaml', '--test-cmd-args=--testoverrides=./testing/experiments/ignore_known_gce_container_restarts.yaml', '--test-cmd-name=ClusterLoaderV2', '--timeout=1050m', '--logexporter-gcs-path=gs://kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-performance/1262790701058363395/artifacts')' returned non-zero exit status 1
E0519 18:36:01.014] Command failed
I0519 18:36:01.015] process 339 exited with code 1 after 92.2m
E0519 18:36:01.015] FAIL: ci-kubernetes-e2e-gce-scale-performance
I0519 18:36:01.015] Call:  gcloud auth activate-service-account --key-file=/etc/service-account/service-account.json
W0519 18:36:01.530] Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
I0519 18:36:01.576] process 127289 exited with code 0 after 0.0m
I0519 18:36:01.576] Call:  gcloud config get-value account
I0519 18:36:01.981] process 127303 exited with code 0 after 0.0m
I0519 18:36:01.982] Will upload results to gs://kubernetes-jenkins/logs using pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com
... skipping 21 lines ...