Closed
Description
Looks as though the windows/arm64 builders are sick / MIA.
farmer.golang.org reports:
Reverse pool by host type (in use / total)
...
host-windows-arm64-mini: 0/0 (6 missing)
host-windows-arm64-zx2c4: 0/0 (1 missing)
host-windows11-arm64-mini: 0/0 (1 missing)
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 .
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done
Relationships
Development
No branches or pull requests
Participants
Activity
cagedmantis commentedon Mar 8, 2022
cc @golang/release
dmitshur commentedon Mar 9, 2022
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.
gopherbot commentedon Mar 9, 2022
Change https://go.dev/cl/391136 mentions this issue:
dashboard: update expectations for windows-arm64 buildersdashboard: update expectations for windows-arm64 builders
gopherbot commentedon Mar 10, 2022
Change https://go.dev/cl/391358 mentions this issue:
env/windows-arm64: disable buildlet password expirationdmitshur commentedon Mar 10, 2022
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.