Skip to content
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

Open
dmitshur opened this issue Dec 29, 2022 · 5 comments
Open

x/build: linux-amd64-wsl builder failing #57517

dmitshur opened this issue Dec 29, 2022 · 5 comments
Assignees
Labels
Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@dmitshur
Copy link
Contributor

The linux-amd64-wsl builder (owned by @mengzhuo) flipped abruptly from almost always passing to almost always failing on December 13, 2022:

image

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:

fatal error: trace: ReadTrace got invalid frequency

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.

@dmitshur dmitshur added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Dec 29, 2022
@dmitshur dmitshur added this to the Backlog milestone Dec 29, 2022
@mengzhuo
Copy link
Contributor

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.

@mengzhuo mengzhuo self-assigned this Dec 30, 2022
@mengzhuo
Copy link
Contributor

mengzhuo commented Jan 2, 2023

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.
2023-1-4: Ian upload a new commit but still failed on wsl. It turns out the firewall of Windows blocked all broadcast pacakge, I've disabled firewall.

@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. Builders x/build issues (builders, bots, dashboards) and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Jan 2, 2023
@dmitshur dmitshur modified the milestones: Backlog, Unreleased Jan 2, 2023
@dmitshur dmitshur changed the title net/http/pprof: "fatal error: trace: ReadTrace got invalid frequency" on linux-amd64-wsl builder as of 2022-12-13 x/build: linux-amd64-wsl builder fails with "fatal error: trace: ReadTrace got invalid frequency" as of 2022-12-13 Jan 2, 2023
@heschi heschi changed the title x/build: linux-amd64-wsl builder fails with "fatal error: trace: ReadTrace got invalid frequency" as of 2022-12-13 x/build: linux-amd64-wsl builder failing Jan 4, 2023
@heschi
Copy link
Contributor

heschi commented Jan 4, 2023

@heschi
Copy link
Contributor

heschi commented Jan 4, 2023

Note also that quite a few x/ repo tests are failing; debug, sys, net look real to me.

@mengzhuo
Copy link
Contributor

mengzhuo commented Jan 6, 2023

@heschi One major difference is builders running on Ubuntu 22.04 LTS from Microsoft store, instead of 20.04 LTS.
I'll take a look at strace log in WSL builder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done.
Projects
Status: In Progress
Development

No branches or pull requests

3 participants