-
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/env/windows-arm64: update OS version #48946
Labels
Builders
x/build issues (builders, bots, dashboards)
FrozenDueToAge
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
Comments
toothrot
added
the
NeedsFix
The path to resolution is known, but the work has not been done.
label
Oct 13, 2021
Rather, just move to the Windows 11 stable branch, build 22000.y at the time of writing. |
Change https://golang.org/cl/377696 mentions this issue: |
gopherbot
pushed a commit
to golang/build
that referenced
this issue
Jan 12, 2022
Add a new host type, host-windows11-arm64-mini. It should support both ARM64 and ARM builds but for starters let's focus on ARM64. For golang/go#48946, golang/go#47019. Change-Id: I7ff07a97661fb6621237b9801ff0d0e338c6d4f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/377696 Trust: Heschi Kreinick <[email protected]> Run-TryBot: Heschi Kreinick <[email protected]> Reviewed-by: Alex Rakoczy <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
The windows 11 ARM64 builder is up and running fairly smoothly (barring #51019) at this point. We still need to decide which to use for the 1.18 release. |
Filed #51085 for the decision. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Builders
x/build issues (builders, bots, dashboards)
FrozenDueToAge
NeedsFix
The path to resolution is known, but the work has not been done.
We're running a relatively old Insider Preview version of Windows that may be causing some of our build failures. We should update to a newer one, especially if it is about to expire.
The text was updated successfully, but these errors were encountered: