(resend, forget to cc bts)
That's the one failed test,
--- FAIL: TestCountMallocs (0.00s)
fmt_test.go:1443: Sprintf(""): got 3 allocs, want <=0
fmt_test.go:1443: Sprintf("xxx"): got 4 allocs, want <=1
fmt_test.go:1443: Sprintf("%x"): got 5 allocs, want <=2
fmt_test.go:1443: Sprintf("%s"): got 5 allocs, want <=2
fmt_test.go:1443: Sprintf("%x %x"): got 5 allocs, want <=3
fmt_test.go:1443: Sprintf("%g"): got 7 allocs, want <=2
fmt_test.go:1443: Fprintf(buf, "%s"): got 4 allocs, want <=1
fmt_test.go:1443: Fprintf(buf, "%x %x %x"): got 4 allocs, want <=0
It happens when you run tests with 1 process(GOMAXPROCS=1)
The upstream bug is https://github.com/golang/go/issues/23000
This test is to ensure max malloc times used, so I don't think the test
is so important to kick packages out of testing.
Can we skip this test?
--
Shengjing Zhu
