Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Download via bazelisk fails with 404 on AARCH64 #16061

Closed
elfringham opened this issue Aug 7, 2022 · 8 comments · Fixed by bazelbuild/bazelisk#346 or bazelbuild/bazelisk#347
Closed
Assignees
Labels
team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. type: bug untriaged

Comments

@elfringham
Copy link

Description of the bug:

If using .bazelversion to specify a commit hash, it fails to download the required artifact with a 404 error like this
$ bazel --version 2022/08/06 09:47:13 Using unreleased version at commit f440f8ec3f63e5d663e1f9d9614f05a39422102a 2022/08/06 09:47:13 Downloading https://storage.googleapis.com/bazel-builds/artifacts/ubuntu1404_arm64/f440f8ec3f63e5d663e1f9d9614f05a39422102a/bazel... 2022/08/06 09:47:13 could not download Bazel: HTTP GET https://storage.googleapis.com/bazel-builds/artifacts/ubuntu1404_arm64/f440f8ec3f63e5d663e1f9d9614f05a39422102a/bazel failed with error 404
Assuming that URL used by bazelisk is correct that suggests that bazel is not building or uploading the AARCH64 binary for intermediate builds referenced only by a commit hash. Is that possible? Or is the URL used not correct?

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Setup .bazelversion like this and using bazelisk 1.12.0
$ cat .bazelversion f440f8ec3f63e5d663e1f9d9614f05a39422102a $ bazel version

Which operating system are you running Bazel on?

Ubuntu 18.04

What is the output of bazel info release?

As above, fails to run

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

n/a

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

`$ git remote get-url origin; git rev-parse master; git rev-parse HEAD
https://github.com/tensorflow/tensorflow.git
6479186fba791386a5962f53c1e2d2cbf51c3dc0
b265fdbcce6b9cd960a4c482a5bd487489fbd641
`

Have you found anything relevant by searching the web?

This is linked to bazelisk issue bazelbuild/bazelisk#317 which seems to have been resolved with the 1.12.0 release, at least at the bazelisk end and assuming that the URL being used is correct.

Any other information, logs, or outputs that you want to share?

No response

@sgowroji
Copy link
Member

sgowroji commented Aug 8, 2022

Hello @elfringham, Could you please provide complete steps to reproduce the above issue. Thanks!

@elfringham
Copy link
Author

elfringham commented Aug 8, 2022

@sgowroji

On a AARCH64 architecture machine
`$ mkdir wksp

$ cd wksp

$ touch WORKSPACE

$ echo f440f8e>.bazelversion

$ wget https://github.com/bazelbuild/bazelisk/releases/download/v1.12.0/bazelisk-linux-arm64

$ chmod +x bazelisk-linux-arm64

$ ./bazelisk-linux-arm64 version

2022/08/08 09:30:31 Using unreleased version at commit f440f8e

022/08/08 09:30:31 Downloading https://storage.googleapis.com/bazel-builds/artifacts/ubuntu1404_arm64/f440f8ec3f63e5d663e1f9d9614f05a39422102a/bazel...

2022/08/08 09:30:31 could not download Bazel: HTTP GET https://storage.googleapis.com/bazel-builds/artifacts/ubuntu1404_arm64/f440f8ec3f63e5d663e1f9d9614f05a39422102a/bazel failed with error 404
`

@sgowroji sgowroji added type: bug team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. untriaged and removed more data needed labels Aug 8, 2022
@elfringham
Copy link
Author

elfringham commented Aug 8, 2022

@sgowroji github keeps turning the git commit hash in the above into a link, which is wrong. You should get this
$ cat .bazelversion f440f8ec3f63e5d663e1f9d9614f05a39422102a

@fweikert
Copy link
Member

fweikert commented Aug 11, 2022

We stopped supporting Ubuntu 14.04 binaries in June 2019: b6d78a5

I wonder why this happens on 18.04, though.

@elfringham
Copy link
Author

@sgowroji What is the reason for the 'more data needed' tag? I do not see a question being asked.

Also FWIW https://storage.googleapis.com/bazel-builds/artifacts/ubuntu1404/f440f8ec3f63e5d663e1f9d9614f05a39422102a/bazel is a valid download link, so while Ubuntu 14.04 may not be a supported platform, for some reason it works as a download link to reach the x86 artifact.

@fweikert fweikert self-assigned this Aug 16, 2022
fweikert added a commit to fweikert/bazelisk that referenced this issue Aug 16, 2022
We stopped publishing binaries for Ubuntu 14.04 some time ago, and we don't upload Arm64 Linux binaries (yet).
Consequently, Bazelisk on Linux should always fetch the regular Ubuntu 18.04 binaries for now.

Fixes bazelbuild/bazel#16061
fweikert added a commit to bazelbuild/bazelisk that referenced this issue Aug 16, 2022
We stopped publishing binaries for Ubuntu 14.04 some time ago, and we don't upload Arm64 Linux binaries (yet).
Consequently, Bazelisk on Linux should always fetch the regular Ubuntu 18.04 binaries for now.

Fixes bazelbuild/bazel#16061
@fweikert
Copy link
Member

@elfringham
Copy link
Author

Not fixed.

@fweikert
Copy link
Member

The real fix would be bazelbuild/continuous-integration#1402

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. type: bug untriaged
Projects
None yet
3 participants