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/ssa: occasional "exit status 541111823" on windows-386-2008 builder #37360

Closed
bcmills opened this issue Feb 21, 2020 · 5 comments
Labels
Builders x/build issues (builders, bots, dashboards) compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@bcmills
Copy link
Contributor

bcmills commented Feb 21, 2020

#!watchflakes
post <- `exit status 541111823`

The test for cmd/compile/internal/ssa occasionally exits with status 541111823 (and no other output) on the windows-386-2008 builder:
2020-02-21T01:48:01-1bc116b/windows-386-2008
2020-01-09T19:50:42-10bfe5b/windows-386-2008

I wonder if perhaps it is running out of address space? I seem to recall that that test is one of the most memory-intensive in the standard library.

CC @dmitshur @cagedmantis @toothrot @alexbrainman @networkimprov @randall77 @josharian @martisch

@bcmills bcmills added OS-Windows Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Feb 21, 2020
@bcmills bcmills added this to the Backlog milestone Feb 21, 2020
@josharian
Copy link
Contributor

Alex, do you know what that exit code means? Googling yields no results.

Possibly related: #36309. The problem there appeared to have been compiling the test; the changes that I just submitted over the last day or so fixed it in that issue by reducing memory required to build package ssa.

If it keeps happening, it’d be useful to know what’s happening when it fails—compiling the test, running the test (which one), etc.

@networkimprov
Copy link

cc @zx2c4 @mattn

@alexbrainman
Copy link
Member

I wonder if perhaps it is running out of address space?

I tried running this test on my computer. And its memory usage does not look any different from any other Go program. I uses Task Manager to view memory performance.

c:\Users\Alex\dev\go\src>go version
go version devel +ebe49b2c29 Sun Feb 23 01:23:41 2020 +0000 windows/386

c:\Users\Alex\dev\go\src>go test -short -count=1 cmd/compile/internal/ssa
ok      cmd/compile/internal/ssa        0.428s

c:\Users\Alex\dev\go\src>go test -short -count=10 cmd/compile/internal/ssa
ok      cmd/compile/internal/ssa        3.165s

Alex, do you know what that exit code means? Googling yields no results.

I don't know. Unfortunately. Usually exit code corresponds to some real Windows error number. But this one does not look like an error number.

I am out of ideas. Sorry.

Alex

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 13, 2022
@mknyszek mknyszek moved this to Triage Backlog in Go Compiler / Runtime Jul 15, 2022
@bcmills bcmills added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label May 12, 2023
@gopherbot
Copy link
Contributor

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@github-project-automation github-project-automation bot moved this from Triage Backlog to Done in Go Compiler / Runtime Jun 12, 2023
@golang golang locked and limited conversation to collaborators Jun 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Builders x/build issues (builders, bots, dashboards) compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
Archived in project
Development

No branches or pull requests

5 participants