Fetch arm64 version when using USE_BAZEL_VERSION=$commit

[meteorcloudy]

Currently even the arm64 version of Bazelisk fetches x86_64 version of Bazel binaries when fetching from a commit hash.

bazelisk/platforms/platforms.go

Line 11 in 9102523

var platforms = map[string]string{"darwin": "macos", "linux": "ubuntu1404", "windows": "windows"}

needs to be updated to include macos_arm64 and windows_arm64.

Although, we currently only publish arm64 Bazel binaries for macOS and Windows, not Linux ...

[meteorcloudy]

/cc @fweikert

[meteorcloudy]

@Wyverald

[fweikert]

I don't have an M1 machine to test, but shouldn't line 35 handle this problem? It's also possible that DarwinFallback() cannot handle commits (just a theory).

[meteorcloudy]

Yeah, I think line 35 only handles release versions (v.LessThan(armSupportVer))

[keith]

See also #303

[elfringham]

Just got bitten by this bug when our CI attempted building TensorFlow overnight for AARCH64 after an update to pick a commit hash for the bazel version.
https://ci.linaro.org/view/All/job/ldcg-python-manylinux-tensorflow-onednn-nightly/140/console

[learning-to-play]

What is the status of this issue? TensorFlow supports ARM64. If USE_BAZEL_VERSION=$commit doesn't work on ARM64, it practically prevents TensorFlow from using this feature.

[keith]

are you using the latest bazelisk release?

[elfringham]

@keith We were using 1.11.0. I just tried it with 1.12.0 and get a different error now, it fails with a 404. So assuming the path now attempted to be downloaded by bazelisk is correct, then maybe this is now a bazel problem in that the artifacts are not being created.
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

[elfringham]

This seems now to be dependent on bazelbuild/continuous-integration#1402 and then having the download block removed that was introduced with #346 and #347