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.

Sign up for GitHub

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

Jump to bottom

cmd/compile: windows-386-gce build is flaky #12519

Closed
josharian opened this issue Sep 6, 2015 · 5 comments
Closed

cmd/compile: windows-386-gce build is flaky #12519

josharian opened this issue Sep 6, 2015 · 5 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Go1.7

Comments

@josharian
Copy link
Contributor

For example, https://storage.googleapis.com/go-build-log/05719e3d/windows-386-gce_41de92d0.log

The master branch builder is stable.

The error message is fatal error: runtime: cannot map pages in arena address space, which appears to be caused by being low on memory.

cc @randall77 @tzneal
@randall77
Copy link
Contributor

We're running with GOGC=off at the moment, which probably makes things (way?) worse than they would otherwise be.

@minux
Copy link
Member

minux commented Sep 6, 2015 via email

@josharian
Copy link
Contributor Author

The failure is during compilation, so GC is on. This is extra memory usage by the SSA compiler.

@rsc rsc modified the milestones: Go1.6, dev.ssa Oct 23, 2015
@bradfitz bradfitz modified the milestones: dev.ssa, Go1.7 Mar 2, 2016
@ianlancetaylor ianlancetaylor changed the title cmd/compile/internal/ssa: windows-386-gce build is flaky cmd/compile: windows-386-gce build is flaky May 16, 2016
@quentinmit quentinmit added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 19, 2016
@aclements
Copy link
Member

@josharian, is this still a problem?

@josharian
Copy link
Contributor Author

build.golang.org says no, not still a problem.

@golang golang locked and limited conversation to collaborators May 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Go1.7
Development

No branches or pull requests
8 participants
@bradfitz @josharian @rsc @quentinmit @minux @aclements @randall77 @gopherbot