This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-02-14 19:29
Elapsed4m9s
Revision
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/0d4df396-e82c-42c9-a2ae-85079d7154cb/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/0d4df396-e82c-42c9-a2ae-85079d7154cb/targets/test
uploadercrier
infra-commit96cadf7b3
pod4ccc8250-4f60-11ea-bee6-7ae328210567
repok8s.io/kubernetes
repo-commit55ea3ac41f6c04e34c3c5b1cfb6e47e4f8cf8d0f
repos{u'k8s.io/kubernetes': u'master:55ea3ac41f6c04e34c3c5b1cfb6e47e4f8cf8d0f'}

No Test Failures!


Error lines from build-log.txt

... skipping 63 lines ...
I0214 19:31:53.250] Build timestamp: 1552322823
I0214 19:31:53.251] Build timestamp as int: 1552322823
W0214 19:31:53.351] Run: ('bazel', 'query', '--keep_going', '--noshow_progress', "kind(.*_binary, rdeps(//... -//vendor/..., //...)) except attr('tags', 'manual', //...)")
W0214 19:31:53.352] $TEST_TMPDIR defined: output root default is '/bazel-scratch/.cache/bazel' and max_idle_secs default is '15'.
W0214 19:32:44.255] DEBUG: /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/bazel_toolchains/rules/rbe_repo.bzl:233:5: Bazel 0.23.2 is used in rbe_autoconfig.
W0214 19:32:44.271] DEBUG: /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/bazel_toolchains/rules/rbe_repo.bzl:408:5: Using checked-in configs.
W0214 19:32:45.260] ERROR: /workspace/k8s.io/kubernetes/cluster/images/hyperkube/BUILD:26:1: no such package '@debian-hyperkube-base-ppc64le//image': Pull command failed: F0214 19:32:38.451409     804 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:92857d647abe8d9c7b4d7160cd5699112afc12fde369082a8ed00688b17928a9: [Errno 104] Connection reset by peer
W0214 19:32:45.261]  (/usr/bin/python /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/puller/file/downloaded --directory /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/debian-hyperkube-base-ppc64le/image --os linux --os-version  --os-features  --architecture ppc64le --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:92857d647abe8d9c7b4d7160cd5699112afc12fde369082a8ed00688b17928a9) and referenced by '//cluster/images/hyperkube:image-internal'
W0214 19:33:15.252] ERROR: /workspace/k8s.io/kubernetes/cluster/images/conformance/BUILD:23:1: no such package '@debian-hyperkube-base-ppc64le//image': Pull command failed: F0214 19:32:38.451409     804 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:92857d647abe8d9c7b4d7160cd5699112afc12fde369082a8ed00688b17928a9: [Errno 104] Connection reset by peer
W0214 19:33:15.253]  (/usr/bin/python /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/puller/file/downloaded --directory /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/debian-hyperkube-base-ppc64le/image --os linux --os-version  --os-features  --architecture ppc64le --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:92857d647abe8d9c7b4d7160cd5699112afc12fde369082a8ed00688b17928a9) and referenced by '//cluster/images/conformance:conformance-internal'
W0214 19:33:16.591] ERROR: /workspace/k8s.io/kubernetes/cluster/images/conformance/BUILD:23:1: no such package '@debian-hyperkube-base-ppc64le//image': Pull command failed: F0214 19:32:38.451409     804 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:92857d647abe8d9c7b4d7160cd5699112afc12fde369082a8ed00688b17928a9: [Errno 104] Connection reset by peer
W0214 19:33:16.593]  (/usr/bin/python /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/puller/file/downloaded --directory /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/debian-hyperkube-base-ppc64le/image --os linux --os-version  --os-features  --architecture ppc64le --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:92857d647abe8d9c7b4d7160cd5699112afc12fde369082a8ed00688b17928a9) and referenced by '//cluster/images/conformance:conformance-internal'
W0214 19:33:16.604] ERROR: /workspace/k8s.io/kubernetes/cluster/images/hyperkube/BUILD:26:1: no such package '@debian-hyperkube-base-ppc64le//image': Pull command failed: F0214 19:32:38.451409     804 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:92857d647abe8d9c7b4d7160cd5699112afc12fde369082a8ed00688b17928a9: [Errno 104] Connection reset by peer
W0214 19:33:16.605]  (/usr/bin/python /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/puller/file/downloaded --directory /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/debian-hyperkube-base-ppc64le/image --os linux --os-version  --os-features  --architecture ppc64le --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:92857d647abe8d9c7b4d7160cd5699112afc12fde369082a8ed00688b17928a9) and referenced by '//cluster/images/hyperkube:image-internal'
W0214 19:33:16.979] ERROR: Evaluation of query "rdeps((//... - //vendor/...), //...)" failed: errors were encountered while computing transitive closure
W0214 19:33:18.327] WARNING: --keep_going specified, ignoring errors.  Results may be inaccurate
W0214 19:33:18.856] Run: ('/workspace/./test-infra/jenkins/../scenarios/../hack/coalesce.py',)
I0214 19:33:19.055] Build passed, tests failed or timed out
E0214 19:33:19.064] Command failed
I0214 19:33:19.064] process 345 exited with code 3 after 1.5m
E0214 19:33:19.065] FAIL: ci-kubernetes-bazel-build
I0214 19:33:19.065] Call:  gcloud auth activate-service-account --key-file=/etc/service-account/service-account.json
W0214 19:33:19.760] Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
I0214 19:33:19.828] process 1032 exited with code 0 after 0.0m
I0214 19:33:19.829] Call:  gcloud config get-value account
I0214 19:33:20.404] process 1045 exited with code 0 after 0.0m
I0214 19:33:20.405] Will upload results to gs://kubernetes-jenkins/logs using pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com
I0214 19:33:20.405] Upload result and artifacts...
I0214 19:33:20.405] Gubernator results at https://gubernator.k8s.io/build/kubernetes-jenkins/logs/ci-kubernetes-bazel-build/1228401011438129153
I0214 19:33:20.405] Call:  gsutil ls gs://kubernetes-jenkins/logs/ci-kubernetes-bazel-build/1228401011438129153/artifacts
W0214 19:33:21.756] CommandException: One or more URLs matched no objects.
E0214 19:33:21.937] Command failed
I0214 19:33:21.937] process 1058 exited with code 1 after 0.0m
W0214 19:33:21.937] Remote dir gs://kubernetes-jenkins/logs/ci-kubernetes-bazel-build/1228401011438129153/artifacts not exist yet
I0214 19:33:21.938] Call:  gsutil -m -q -o GSUtil:use_magicfile=True cp -r -c -z log,txt,xml /workspace/_artifacts gs://kubernetes-jenkins/logs/ci-kubernetes-bazel-build/1228401011438129153/artifacts
I0214 19:33:24.640] process 1203 exited with code 0 after 0.0m
W0214 19:33:24.640] metadata path /workspace/_artifacts/metadata.json does not exist
W0214 19:33:24.641] metadata not found or invalid, init with empty metadata
... skipping 15 lines ...