-
Notifications
You must be signed in to change notification settings - Fork 18k
x/build, runtime: Windows arm64 builder fail to allocate memory #73254
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
Comments
Related Issues (Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
Indeed. Thanks for filing this issue and de-duplicating all the related watchflakes reports. The "yesterday afternoon" update was likely an automated one rather than something we did manually. I've restarted both builders, and they seem to be back to working okay. We still have #66962 open that tracks the occasional problems with the builder, though they seem to have been much more stable in the recent months, and this is one instance when they weren't. Closing this. |
The
gotip-windows-arm64
bots were updated yesterday afternoon, and since then all CI runs fail becauseVirtualAlloc
returnsERROR_COMMITMENT_LIMIT
. See for example https://ci.chromium.org/ui/p/golang/builders/ci/gotip-windows-arm64/b8718210226708771345/test-results?sortby=&groupby=.This is probably a configuration issue, although maybe rebooting the boot also solve it. Don't have permissions to do that myself. @dmitshur
The text was updated successfully, but these errors were encountered: