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: TestBigGOMAXPROCS failures on windows-386-2008 builder #38541

Closed
bcmills opened this issue Apr 20, 2020 · 1 comment
Closed

runtime: TestBigGOMAXPROCS failures on windows-386-2008 builder #38541

bcmills opened this issue Apr 20, 2020 · 1 comment
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker
Milestone

Comments

@bcmills
Copy link
Contributor

bcmills commented Apr 20, 2020

runtime_test.TestBigGOMAXPROCS (added in CL 228420 for #38474) is showing several failures on the windows-386-2008 builder.

2020-04-19T07:51:23-d0d0028/windows-386-2008
2020-04-19T03:23:59-af9ab6b/windows-386-2008
2020-04-17T19:18:12-ef5c59d/windows-386-2008

Marking as release-blocker since this test is new in 1.15.

(It isn't clear to me whether this failure mode is related to the one on the linux-amd64-staticlockranking builder.)

CC @ianlancetaylor @prattmic @andybons @danscales

@bcmills bcmills added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker labels Apr 20, 2020
@bcmills bcmills added this to the Go1.15 milestone Apr 20, 2020
@gopherbot
Copy link

Change https://golang.org/cl/229077 mentions this issue: runtime: skip TestBigGOMAXPROCS if it runs out of memory

@golang golang locked and limited conversation to collaborators Apr 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker
Projects
None yet
Development

No branches or pull requests

2 participants