You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to run a build on my machine and it gets stuck on different places of the build but all have to do with fetching. Every run locks up in different places. I have a very flaky internet connection and, while I can't tie every time the build freezes to a connection drop, I've found my connection is a good test for if code has good retry logic.
I've attached the output of a build that I let sit for over a day. As well I've attached a multiple back-to-back runs that I kill once I see they're stuck.
Any help would be greatly appreciated.
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I'm not sure, I just run bazel build //... in my repo.
Which operating system are you running Bazel on?
macOS 12.4 Monterey
What is the output of bazel info release?
5.2.0
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
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
git@github.com:<redacted>/<redacted>.git
master
fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
e87d1c637a0c7ffb3738be9ecb85c2395bbae07f
Have you found anything relevant by searching the web?
Description of the bug:
I'm trying to run a build on my machine and it gets stuck on different places of the build but all have to do with fetching. Every run locks up in different places. I have a very flaky internet connection and, while I can't tie every time the build freezes to a connection drop, I've found my connection is a good test for if code has good retry logic.
I've attached the output of a build that I let sit for over a day. As well I've attached a multiple back-to-back runs that I kill once I see they're stuck.
Any help would be greatly appreciated.
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I'm not sure, I just run
bazel build //...
in my repo.Which operating system are you running Bazel on?
macOS 12.4 Monterey
What is the output of
bazel info release
?5.2.0
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
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?
#748
Any other information, logs, or outputs that you want to share?
I tried to run it as long as I could but finally just terminated with
ctrl-\
as mentioned in #748 . Here is the outputThe text was updated successfully, but these errors were encountered: