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 tried making a change to cmd/go/internal/cache to replace uses of fmt.Sprintf("%02x", i) with hex.EncodeToString. You can view the change here: https://go-review.googlesource.com/c/go/+/258039
The change didn't work, which is fine. However, instead of giving me an error message or explaining what went wrong, run.bash and all.bash just hung for over an hour with no output on the Building Go toolchain2 using go_bootstrap and Go toolchain1 line, which you can see here as of Wednesday at 5:30pm Pacific. https://farmer.golang.org/try?commit=f4ae3966
In fact, most of the Trybot builders appear to be stuck for multiple hours on that step, which isn't great since there appears to be no way to cancel a Trybot build.
I would expect compilation to either succeed or fail with an error, or time out with an error, instead of hanging indefinitely. I still don't know what's wrong with the CL.
The text was updated successfully, but these errors were encountered:
I tried making a change to cmd/go/internal/cache to replace uses of
fmt.Sprintf("%02x", i)
withhex.EncodeToString
. You can view the change here: https://go-review.googlesource.com/c/go/+/258039The change didn't work, which is fine. However, instead of giving me an error message or explaining what went wrong,
run.bash
andall.bash
just hung for over an hour with no output on theBuilding Go toolchain2 using go_bootstrap and Go toolchain1
line, which you can see here as of Wednesday at 5:30pm Pacific. https://farmer.golang.org/try?commit=f4ae3966In fact, most of the Trybot builders appear to be stuck for multiple hours on that step, which isn't great since there appears to be no way to cancel a Trybot build.
I would expect compilation to either succeed or fail with an error, or time out with an error, instead of hanging indefinitely. I still don't know what's wrong with the CL.
The text was updated successfully, but these errors were encountered: