-
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: linux-amd64-wsl builder failing #57517
Comments
The WSL builders were based on ESXi 6.7 before Dec 13th, however my license are expired on that day. So I changed to PVE instead now. Maybe I can change to ESXi 7.0 for free usage. |
Updates: I've transfered all wsl builder to new esxi based server, but there is no new commit so I think we need to wait for it to close this issue. |
Still looks busted? https://build.golang.org/log/2d1e14595ca6ef409f849aa8eab0afced9c43623 |
Note also that quite a few x/ repo tests are failing; debug, sys, net look real to me. |
@heschi One major difference is builders running on Ubuntu 22.04 LTS from Microsoft store, instead of 20.04 LTS. |
Updates: I will look into why Ubuntu 22.04 LTS still failed builds. |
@mengzhuo Should we close this issue since the builder is green again? Then maybe add an issue to explore why the Ubuntu 22.04 based builder was failing? |
The linux-amd64-wsl builder (owned by @mengzhuo) flipped abruptly from almost always passing to almost always failing on December 13, 2022:
On the main branch, it happened first on CL 457055 on Dec 13. But it also started happening on 1.19 and 1.18 release branches on a completely unrelated change (CL 456560 and 456561) on Dec 14. This suggests that the failure is more likely to be caused by something that happened on that week rather than a particular code change.
The most common error is:
Here are the 3 most recent build logs:
@mengzhuo Do you know if there were changes to the builder or its environment around Dec 13?
CC @golang/runtime, @golang/release.
The text was updated successfully, but these errors were encountered: