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.

cc @zx2c4 @mattn

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

2020-04-15T03:25:21-8f53fad/windows-386-2008
2020-04-13T17:38:02-614a713/windows-386-2008
2020-04-12T15:37:29-3afa741/windows-386-2008
2020-03-24T00:04:19-6a9d850/windows-386-2008

And none from before 2020-01-09.

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.)