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

x/text: FAIL: TestCountMallocs #23000

Open
nicolasStevenin opened this issue Dec 5, 2017 · 1 comment
Open

x/text: FAIL: TestCountMallocs #23000

nicolasStevenin opened this issue Dec 5, 2017 · 1 comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@nicolasStevenin
Copy link

Hello !

What version of Go are you using (go version)? 1.8

Does this issue reproduce with the latest release? version 0.1.0

What did you do?

I try to test message in the project github.com/golang/text/ in version 0.1.0 it fails with
--- FAIL: TestCountMallocs (0.00s)
fmt_test.go:1443: Sprintf("%x"): got 3 allocs, want <=2
fmt_test.go:1443: Sprintf("%s"): got 3 allocs, want <=2
fmt_test.go:1443: Sprintf("%x %x"): got 4 allocs, want <=3
fmt_test.go:1443: Sprintf("%g"): got 5 allocs, want <=2
fmt_test.go:1443: Fprintf(buf, "%s"): got 2 allocs, want <=1
fmt_test.go:1443: Fprintf(buf, "%x %x %x"): got 1 allocs, want <=0
FAIL
exit status 1
FAIL golang.org/x/text/message 0.023s

Thank you for your help

@gopherbot gopherbot added this to the Unreleased milestone Dec 5, 2017
@ALTree
Copy link
Member

ALTree commented Dec 5, 2017

I can reproduce this with go1.9 too. I think we don't hit it on the builders because the test is skipped if GOMAXPROCS > 1, but it's easily reproduced with GOMAXPROCS=1 go test -run=TestCountMallocs

cc @mpvl

@ALTree ALTree added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Dec 5, 2017
@ALTree ALTree changed the title x/text : FAIL: TestCountMallocs x/text: FAIL: TestCountMallocs Dec 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

3 participants