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/arm: unrecognized failures #71033

Closed
gopherbot opened this issue Dec 26, 2024 · 3 comments
Closed

cmd/compile/internal/arm: unrecognized failures #71033

gopherbot opened this issue Dec 26, 2024 · 3 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@gopherbot
Copy link
Contributor

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

Issue created automatically to collect these failures.

Example (log):

FAIL	cmd/compile/internal/arm [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 Dec 26, 2024
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "cmd/compile/internal/arm" && test == ""
2024-12-24 01:53 gotip-darwin-amd64_13 go@772f024c cmd/compile/internal/arm (log)
FAIL	cmd/compile/internal/arm [build failed]

watchflakes

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Dec 26, 2024
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

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

watchflakes

@mknyszek
Copy link
Contributor

The netbsd failure looks like an OOM or timeout. Not too interesting. The Darwin failure has a ton of 0xb01dfacedebac1e addresses which are scarier; per Keith it's the address we print when we don't know what address we actually failed on because the OS wouldn't tell us. Many binaries fail this way.

Since there's only one failure, maybe this is a transient infra failure?

@mknyszek mknyszek added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jan 15, 2025
@mknyszek mknyszek added this to the Backlog milestone Jan 15, 2025
@mknyszek mknyszek removed the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jan 15, 2025
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. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: Done
Development

No branches or pull requests

2 participants