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
build: disable linux/arm trybot #22592
Comments
The linux-arm builder is currently running for 49 minutes on the trybot for my last CL. |
Sounds like a dup of #21839. @adams-sarah, did you ever make progress on debugging it? |
Yea, dupe of my other issue. I assume it is a network issue though. Didn’t the scaleway people say that moving our builders to Tokyo would give us a much slower external network conn? I think you were on that thread. It’s the write to GCS that’s taking forever. |
It was the arm64 builders (packet.net) that moved us to Tokyo, not Scaleway (still in Paris). |
My apologies. You’re totally right. |
Another, this one at 122 min (>2 hours!!).
This is making Run-TryBot essentially useless. It seems like we should turn off the linux-arm trybot until this is fixed. |
Change https://golang.org/cl/77370 mentions this issue: |
Fixes golang/go#21839 Updates golang/go#22592 Change-Id: Ia96236c61847193f930564b4dd5e0d7965e89945 Reviewed-on: https://go-review.googlesource.com/77370 Reviewed-by: Andrew Bonventre <andybons@golang.org>
Change https://golang.org/cl/78032 mentions this issue: |
As I write this, https://farmer.golang.org/try?commit=5728eb6a says the linux-arm buildbot has been running for 26.1 min.
It's now T21:59 or so.
I am not sure what's going on or how to find out. It may be related to my cmd/go changes, or not.
/cc @bradfitz
The text was updated successfully, but these errors were encountered: