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 17:54
Elapsed4m37s
Revisionrelease-1.15
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/d0675ee1-a879-4eab-b6fe-4ae542241842/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/d0675ee1-a879-4eab-b6fe-4ae542241842/targets/test
uploadercrier

No Test Failures!


Error lines from build-log.txt

... skipping 8 lines ...
Build timestamp: 1552322823
Build timestamp as int: 1552322823
Run: ('bazel', 'query', '--keep_going', '--noshow_progress', "kind(.*_binary, rdeps(//... -//vendor/..., //...)) except attr('tags', 'manual', //...)")
$TEST_TMPDIR defined: output root default is '/bazel-scratch/.cache/bazel' and max_idle_secs default is '15'.
DEBUG: /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/bazel_toolchains/rules/rbe_repo.bzl:233:5: Bazel 0.23.2 is used in rbe_autoconfig.
DEBUG: /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/bazel_toolchains/rules/rbe_repo.bzl:408:5: Using checked-in configs.
ERROR: /home/prow/go/src/github.com/kubernetes/kubernetes/cluster/images/hyperkube/BUILD:4:1: no such package '@debian-hyperkube-base-arm//image': Pull command failed: F0214 17:58:48.351421     451 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:73260814af61522ff6aa48291df457d3bb0a91c4bf72e7cfa51fbaf03eb65fae: [Errno 104] Connection reset by peer
 (/usr/bin/python /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/puller/file/downloaded --directory /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/debian-hyperkube-base-arm/image --os linux --os-version  --os-features  --architecture arm --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:73260814af61522ff6aa48291df457d3bb0a91c4bf72e7cfa51fbaf03eb65fae) and referenced by '//cluster/images/hyperkube:hyperkube-internal'
ERROR: /home/prow/go/src/github.com/kubernetes/kubernetes/cluster/images/conformance/BUILD:22:1: no such package '@debian-hyperkube-base-arm//image': Pull command failed: F0214 17:58:48.351421     451 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:73260814af61522ff6aa48291df457d3bb0a91c4bf72e7cfa51fbaf03eb65fae: [Errno 104] Connection reset by peer
 (/usr/bin/python /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/puller/file/downloaded --directory /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/debian-hyperkube-base-arm/image --os linux --os-version  --os-features  --architecture arm --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:73260814af61522ff6aa48291df457d3bb0a91c4bf72e7cfa51fbaf03eb65fae) and referenced by '//cluster/images/conformance:conformance-internal'
ERROR: /home/prow/go/src/github.com/kubernetes/kubernetes/cluster/images/hyperkube/BUILD:4:1: no such package '@debian-hyperkube-base-arm//image': Pull command failed: F0214 17:58:48.351421     451 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:73260814af61522ff6aa48291df457d3bb0a91c4bf72e7cfa51fbaf03eb65fae: [Errno 104] Connection reset by peer
 (/usr/bin/python /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/puller/file/downloaded --directory /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/debian-hyperkube-base-arm/image --os linux --os-version  --os-features  --architecture arm --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:73260814af61522ff6aa48291df457d3bb0a91c4bf72e7cfa51fbaf03eb65fae) and referenced by '//cluster/images/hyperkube:hyperkube-internal'
ERROR: /home/prow/go/src/github.com/kubernetes/kubernetes/cluster/images/conformance/BUILD:22:1: no such package '@debian-hyperkube-base-arm//image': Pull command failed: F0214 17:58:48.351421     451 __main__.py:133] Error pulling and saving image k8s.gcr.io/debian-hyperkube-base@sha256:73260814af61522ff6aa48291df457d3bb0a91c4bf72e7cfa51fbaf03eb65fae: [Errno 104] Connection reset by peer
 (/usr/bin/python /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/puller/file/downloaded --directory /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/external/debian-hyperkube-base-arm/image --os linux --os-version  --os-features  --architecture arm --variant  --features  --name k8s.gcr.io/debian-hyperkube-base@sha256:73260814af61522ff6aa48291df457d3bb0a91c4bf72e7cfa51fbaf03eb65fae) and referenced by '//cluster/images/conformance:conformance-internal'
ERROR: Evaluation of query "rdeps((//... - //vendor/...), //...)" failed: errors were encountered while computing transitive closure
WARNING: --keep_going specified, ignoring errors.  Results may be inaccurate
Run: ('/home/prow/go/src/github.com/kubernetes/kubernetes/../test-infra/scenarios/../hack/coalesce.py',)
Build passed, tests failed or timed out