-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Download via bazelisk fails with 404 on AARCH64 #16061
Comments
Hello @elfringham, Could you please provide complete steps to reproduce the above issue. Thanks! |
On a AARCH64 architecture machine $ 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 github keeps turning the git commit hash in the above into a link, which is wrong. You should get this |
We stopped supporting Ubuntu 14.04 binaries in June 2019: b6d78a5 I wonder why this happens on 18.04, though. |
@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. |
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
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
https://github.com/bazelbuild/bazelisk/releases/tag/v1.12.1 contains the fix |
Not fixed. |
The real fix would be bazelbuild/continuous-integration#1402 |
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
returnsdevelopment 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
?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
The text was updated successfully, but these errors were encountered: