Florian Weikert
Florian Weikert
Fixed in Bazelisk (for MacOS).
Is this issue still relevant? I'm working on adding more ARM64 machines to our CI.
Some tests require fixes: https://github.com/bazelbuild/bazel/labels/m1-ci
This happened in two steps, "macOS" and "Test on macOS". In both cases I had to retry until the job was assigned to a different agent (macpro-1 in this case).
I've disabled the Buildkite agent for now, since I keep running into this issue. I hope I can find some time for actually debugging the issue.
Just happened again: https://buildkite.com/bazel-trusted/bazel-release/builds/1337#018d17ba-e8ac-44b1-9cff-fa644db58824
And again: https://buildkite.com/bazel-trusted/bazel-release/builds/1348#018d7a61-d78f-41ac-91a3-05acdd40d77b I suspect this might have something to do with the git mirror.
I reset the git mirror - let's see if that solves the problem.
The unofficial policy has been to accept community contributions to the Python version, but we (Bazel team) release new features for the Go version only. The JS version seems to...
Someone in the Bazel team should fix @remote_coverage_tools