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

runtime:cpu4: TestBigGOMAXPROCS failures #69748

Open
gopherbot opened this issue Oct 2, 2024 · 1 comment
Open

runtime:cpu4: TestBigGOMAXPROCS failures #69748

gopherbot opened this issue Oct 2, 2024 · 1 comment
Assignees
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 == "runtime:cpu4" && test == "TestBigGOMAXPROCS"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestBigGOMAXPROCS
=== PAUSE TestBigGOMAXPROCS

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 Oct 2, 2024
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime:cpu4" && test == "TestBigGOMAXPROCS"
2024-10-02 15:54 gotip-windows-386 go@03103a54 runtime:cpu4.TestBigGOMAXPROCS [ABORT] (log)
=== RUN   TestBigGOMAXPROCS
=== PAUSE TestBigGOMAXPROCS

watchflakes

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Oct 2, 2024
@mknyszek mknyszek self-assigned this Oct 2, 2024
@mknyszek mknyszek modified the milestones: Backlog, Go1.24 Oct 2, 2024
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: No status
Development

No branches or pull requests

2 participants