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

bazelisk sometimes fails to download Bazel binaries #626

Closed
werkt opened this issue Oct 11, 2024 · 2 comments · Fixed by #627
Closed

bazelisk sometimes fails to download Bazel binaries #626

werkt opened this issue Oct 11, 2024 · 2 comments · Fixed by #627

Comments

@werkt
Copy link

werkt commented Oct 11, 2024

The ubuntu22 image (and probably others) have a bazelisk that precedes a number of fixes in golang with http fetches, notably identified in googleapis/google-cloud-go#7440

2024/10/09 13:25:45 could not download Bazel: failed to download bazel: failed to download bazel: could not copy from https://releases.bazel.build/7.3.2/release/bazel-7.3.2-linux-x86_64 to /var/lib/buildkite-agent/.cache/bazelisk/downloads/_tmp/download1376248149: stream error: stream ID 1; INTERNAL_ERROR; received from peer

is the reported error, and I expect that with a newer bazelisk (current on image is 1.19, likely running against older golangs) like 1.22 with golang 1.23 basis, this situation should be improved.

@meteorcloudy
Copy link
Member

I rebuilt all docker containers after bazelbuild/continuous-integration#2055, Bazelisk should be updated.

@meteorcloudy meteorcloudy reopened this Nov 5, 2024
@meteorcloudy meteorcloudy transferred this issue from bazelbuild/continuous-integration Nov 5, 2024
@meteorcloudy meteorcloudy changed the title Requesting a rebuild of ubuntu22 with recent bazelisk bazelisk sometimes fails to download Bazel binaries Nov 5, 2024
@meteorcloudy
Copy link
Member

This is still happening on Bazel CI: see failed jobs in https://buildkite.com/bazel/bcr-presubmit/builds/8565#0192e691-f5e4-43fd-afda-c2b24fe85137

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants