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

cmd/compile/internal/arm64: unrecognized failures #71170

Open
gopherbot opened this issue Jan 8, 2025 · 3 comments
Open

cmd/compile/internal/arm64: unrecognized failures #71170

gopherbot opened this issue Jan 8, 2025 · 3 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-NetBSD
Milestone

Comments

@gopherbot
Copy link
Contributor

#!watchflakes
default <- pkg == "cmd/compile/internal/arm64" && test == ""

Issue created automatically to collect these failures.

Example (log):

FAIL	cmd/compile/internal/arm64 [build failed]

watchflakes

@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jan 8, 2025
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "cmd/compile/internal/arm64" && test == ""
2025-01-07 17:56 gotip-netbsd-arm go@9d0772b2 cmd/compile/internal/arm64 (log)
FAIL	cmd/compile/internal/arm64 [build failed]

watchflakes

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jan 8, 2025
@mknyszek
Copy link
Contributor

This is an OOM or timeout on netbsd/arm.

CC @golang/netbsd

@bsiegert
Copy link
Contributor

There is some general flakiness on the two NetBSD/arm build machines. It appeared around the time I switched from gobuilder to LUCI, and also from NetBSD-9 to NetBSD-10. I am still working on getting to the bottom of this, sorry for the noise.

One of the symptoms I am seeing (unrelated?) is that the machine sometimes gets some processes stuck in the "tstile" state. This mostly happens with gopls tests. I suspect a kernel bug, but debugging is difficult because the issue is intermittent.

There is https://gnats.netbsd.org/58871 on the NetBSD side to track this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-NetBSD
Projects
Status: No status
Development

No branches or pull requests

3 participants