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: TestGcSys fails on Windows #27156

Open
bradfitz opened this Issue Aug 22, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@bradfitz
Member

bradfitz commented Aug 22, 2018

--- FAIL: TestGcSys (0.06s)
    gc_test.go:27: expected "OK\n", but got "using too much memory: 39882752 bytes\n"
FAIL

Exposed by https://go-review.googlesource.com/122576 (for #23343)

@bradfitz bradfitz added this to the Go1.12 milestone Aug 22, 2018

@gopherbot

This comment has been minimized.

gopherbot commented Aug 22, 2018

Change https://golang.org/cl/130875 mentions this issue: runtime: skip TestGcSys on Windows

gopherbot pushed a commit that referenced this issue Aug 22, 2018

runtime: skip TestGcSys on Windows
This is causing failures on TryBots and BuildBots:
--- FAIL: TestGcSys (0.06s)
    gc_test.go:27: expected "OK\n", but got "using too much memory: 39882752 bytes\n"
FAIL

Updates #27156

Change-Id: I418bbec89002574cd583c97422e433f042c07492
Reviewed-on: https://go-review.googlesource.com/130875
Run-TryBot: Martin Möhrmann <moehrmann@google.com>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>

komuw added a commit to komuw/go that referenced this issue Dec 4, 2018

runtime: skip TestGcSys on Windows
This is causing failures on TryBots and BuildBots:
--- FAIL: TestGcSys (0.06s)
    gc_test.go:27: expected "OK\n", but got "using too much memory: 39882752 bytes\n"
FAIL

Updates golang#27156

Change-Id: I418bbec89002574cd583c97422e433f042c07492
Reviewed-on: https://go-review.googlesource.com/130875
Run-TryBot: Martin Möhrmann <moehrmann@google.com>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment