go
go copied to clipboard
x/build/env/windows/arm64: windows/arm64 builders are down
windows\arm64
builders have been unresponsive since December 12. First failing CL was https://go-review.googlesource.com/c/go/+/456835, which doesn't seem related.
Is this a planed-long downtime? Is there an ETA for having them up an running again? I have a couple of CLs stuck due to this issue.
@cagedmantis @heschi @dmitshur
Yeah, unfortunately we've lost our builders and not yet replaced them. @thanm may know more about progress here.
Change https://go.dev/cl/460296 mentions this issue: internal/releasetargets: remove windows-arm64 for now
Is the expectation that these will be brought back when the builders are available?
@jaredpar yes
Change https://go.dev/cl/451275 mentions this issue: env/windows-arm64: initial Azure VM support
Change https://go.dev/cl/460837 mentions this issue: dashboard: add windows-arm64 back in using azure vms
Change https://go.dev/cl/460836 mentions this issue: cmd/buildlet/stage0: add windows/arm64 azure support
Change https://go.dev/cl/461097 mentions this issue: env/windows-arm64/azure: add stage zero loop script
Change https://go.dev/cl/461255 mentions this issue: internal/releasetargts: add windows-arm64 again
Builders are back up. I'm going to keep the issue open for a bit longer in case other problems arise, but for now it looks like things are working.
Builders are back up. I'm going to keep the issue open for a bit longer in case other problems arise, but for now it looks like things are working.
Good news!
@thanm I'm still not able to trigger the windows-arm64 builders from a CL (by posting TRY=windows-arm64
), see for example https://go-review.googlesource.com/c/go/+/454675. Is there something missing?
@qmuntal as far as I know there aren't any remaining issues/problems. We had to do a test fix backport for the release branches, but other than that I think things are working. I'll go ahead and close out the bug, we can reopen later if need be. Thanks.
@qmuntal I don't see the TRY=
comment on that CL? The alias does exist: https://cs.opensource.google/go/x/build/+/master:dashboard/builders.go;l=103;drc=faea4fa6b0c3ed3cd8232c6eb6742d3bcb3f867d.
@qmuntal I don't see the
TRY=
comment on that CL? The alias does exist: https://cs.opensource.google/go/x/build/+/master:dashboard/builders.go;l=103;drc=faea4fa6b0c3ed3cd8232c6eb6742d3bcb3f867d.
Here it is: https://go-review.googlesource.com/c/go/+/452995/comments/ba8287b7_ae1d5bac
Oh, it was too old to see. I believe you need to repeat it every time you trigger trybots. https://github.com/golang/go/wiki/SlowBots#pitfalls
Change https://go.dev/cl/462015 mentions this issue: env/windows-arm64/azure: fill in a few missing README bits
Change https://go.dev/cl/462516 mentions this issue: env/windows-arm64/azure: update instructions
Change https://go.dev/cl/462655 mentions this issue: env/windows-arm64/aws: delete