This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-02-17 03:00
Elapsed2m42s
Revision
Buildergke-prow-default-pool-cf4891d4-xxpr
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/64f49179-df50-47a6-95a9-dee5d3108219/targets/test'}}
pod89d32436-5131-11ea-bee6-7ae328210567
resultstorehttps://source.cloud.google.com/results/invocations/64f49179-df50-47a6-95a9-dee5d3108219/targets/test
infra-commitf5dd3ee0e
pod89d32436-5131-11ea-bee6-7ae328210567
repok8s.io/kubernetes
repo-commit48def7e7c32ac6d68c53ce24b33c92aede537fdd
repos{u'k8s.io/kubernetes': u'master:48def7e7c32ac6d68c53ce24b33c92aede537fdd'}

No Test Failures!


Error lines from build-log.txt

... skipping 63 lines ...
I0217 03:01:38.103] Build timestamp: 1552322823
I0217 03:01:38.103] Build timestamp as int: 1552322823
W0217 03:01:38.204] Run: ('bazel', 'query', '--keep_going', '--noshow_progress', "kind(.*_binary, rdeps(//... -//vendor/..., //...)) except attr('tags', 'manual', //...)")
W0217 03:01:38.204] $TEST_TMPDIR defined: output root default is '/bazel-scratch/.cache/bazel' and max_idle_secs default is '15'.
W0217 03:02:13.496] 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.
W0217 03:02:13.498] DEBUG: /bazel-scratch/.cache/bazel/_bazel_root/e9f728bbd90b3fba632eb31b20e1dacd/external/bazel_toolchains/rules/rbe_repo.bzl:408:5: Using checked-in configs.
W0217 03:02:17.378] ERROR: /workspace/k8s.io/kubernetes/cluster/images/hyperkube/BUILD:26:1: no such package '@debian-hyperkube-base-s390x//image': Pull command failed: F0217 03:02:13.849371     817 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:c11d74fa0538c67238576c247bfaddf95ebaa90cd03cb4d2f2ac3c6ebe0441e2: [Errno 104] Connection reset by peer
W0217 03:02:17.379]  (/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-s390x/image --os linux --os-version  --os-features  --architecture s390x --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:c11d74fa0538c67238576c247bfaddf95ebaa90cd03cb4d2f2ac3c6ebe0441e2) and referenced by '//cluster/images/hyperkube:image-internal'
W0217 03:02:39.469] ERROR: /workspace/k8s.io/kubernetes/cluster/images/conformance/BUILD:23:1: no such package '@debian-hyperkube-base-s390x//image': Pull command failed: F0217 03:02:13.849371     817 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:c11d74fa0538c67238576c247bfaddf95ebaa90cd03cb4d2f2ac3c6ebe0441e2: [Errno 104] Connection reset by peer
W0217 03:02:39.470]  (/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-s390x/image --os linux --os-version  --os-features  --architecture s390x --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:c11d74fa0538c67238576c247bfaddf95ebaa90cd03cb4d2f2ac3c6ebe0441e2) and referenced by '//cluster/images/conformance:conformance-internal'
W0217 03:02:40.160] ERROR: /workspace/k8s.io/kubernetes/cluster/images/hyperkube/BUILD:26:1: no such package '@debian-hyperkube-base-s390x//image': Pull command failed: F0217 03:02:13.849371     817 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:c11d74fa0538c67238576c247bfaddf95ebaa90cd03cb4d2f2ac3c6ebe0441e2: [Errno 104] Connection reset by peer
W0217 03:02:40.161]  (/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-s390x/image --os linux --os-version  --os-features  --architecture s390x --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:c11d74fa0538c67238576c247bfaddf95ebaa90cd03cb4d2f2ac3c6ebe0441e2) and referenced by '//cluster/images/hyperkube:image-internal'
W0217 03:02:40.549] ERROR: /workspace/k8s.io/kubernetes/cluster/images/conformance/BUILD:23:1: no such package '@debian-hyperkube-base-s390x//image': Pull command failed: F0217 03:02:13.849371     817 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:c11d74fa0538c67238576c247bfaddf95ebaa90cd03cb4d2f2ac3c6ebe0441e2: [Errno 104] Connection reset by peer
W0217 03:02:40.552]  (/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-s390x/image --os linux --os-version  --os-features  --architecture s390x --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:c11d74fa0538c67238576c247bfaddf95ebaa90cd03cb4d2f2ac3c6ebe0441e2) and referenced by '//cluster/images/conformance:conformance-internal'
W0217 03:02:40.818] ERROR: Evaluation of query "rdeps((//... - //vendor/...), //...)" failed: errors were encountered while computing transitive closure
W0217 03:02:41.791] WARNING: --keep_going specified, ignoring errors.  Results may be inaccurate
W0217 03:02:42.120] Run: ('/workspace/./test-infra/jenkins/../scenarios/../hack/coalesce.py',)
I0217 03:02:42.309] Build passed, tests failed or timed out
E0217 03:02:42.316] Command failed
I0217 03:02:42.316] process 345 exited with code 3 after 1.2m
E0217 03:02:42.317] FAIL: ci-kubernetes-bazel-build
I0217 03:02:42.317] Call:  gcloud auth activate-service-account --key-file=/etc/service-account/service-account.json
W0217 03:02:42.899] Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
I0217 03:02:42.964] process 991 exited with code 0 after 0.0m
I0217 03:02:42.964] Call:  gcloud config get-value account
I0217 03:02:43.453] process 1004 exited with code 0 after 0.0m
I0217 03:02:43.454] Will upload results to gs://kubernetes-jenkins/logs using pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com
I0217 03:02:43.454] Upload result and artifacts...
I0217 03:02:43.454] Gubernator results at https://gubernator.k8s.io/build/kubernetes-jenkins/logs/ci-kubernetes-bazel-build/1229239018739208195
I0217 03:02:43.455] Call:  gsutil ls gs://kubernetes-jenkins/logs/ci-kubernetes-bazel-build/1229239018739208195/artifacts
W0217 03:02:44.605] CommandException: One or more URLs matched no objects.
E0217 03:02:44.783] Command failed
I0217 03:02:44.783] process 1017 exited with code 1 after 0.0m
W0217 03:02:44.783] Remote dir gs://kubernetes-jenkins/logs/ci-kubernetes-bazel-build/1229239018739208195/artifacts not exist yet
I0217 03:02:44.784] 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/1229239018739208195/artifacts
I0217 03:02:46.714] process 1162 exited with code 0 after 0.0m
W0217 03:02:46.714] metadata path /workspace/_artifacts/metadata.json does not exist
W0217 03:02:46.714] metadata not found or invalid, init with empty metadata
... skipping 15 lines ...