-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/build: windows-arm64 builders are missing #51546
Comments
cc @golang/release |
We've identified a problem related to the builders getting stuck on the login screen, and I'm working on resolving it this week. The missing windows-arm64-11 builder is used in the release process for Go 1.18, so I'll update this to be a release-blocker for it until the builders are back. |
Change https://go.dev/cl/391136 mentions this issue: |
Update the expected number of reverse buildlets to describe the current state more accurately. Update the windows-arm64 alias to point to windows-arm64-11, since it's more available and used for most recent releases. For golang/go#51546. Updates golang/go#47019. Change-Id: I5ae1a764efd21da4155ab002f20ad974b098b023 Reviewed-on: https://go-review.googlesource.com/c/build/+/391136 Reviewed-by: Carlos Amedee <carlos@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org>
Change https://go.dev/cl/391358 mentions this issue: |
The builder images have been updated so they're no longer getting stuck, and they're back on farmer.golang.org (along with the corrected expected count—it's currently 5 windows-arm64-11 and 2 windows-arm64-10 builders):
(These builders briefly disconnect in between builds, so it is normal that some are missing at points in time. As long as they reconnect within a few mins, it's working as intended.) This is resolved, so closing. |
Looks as though the windows/arm64 builders are sick / MIA.
farmer.golang.org reports:
Looks like no builder activity on recent CLs:
I went back through the status page and it looks like windows-arm64-zx2c4 has been out for quite some time. Last CL to have a windows-arm64 run was this one on March 4th .
The text was updated successfully, but these errors were encountered: