On Thu, Mar 7, 2013 at 5:03 AM, minux <minux.ma@gmail.com> wrote: > this is strange, ...
12 years, 8 months ago
(2013-03-07 14:18:37 UTC)
#9
On Thu, Mar 7, 2013 at 5:03 AM, minux <minux.ma@gmail.com> wrote:
> this is strange, testing.AllocsPerRun already force GOMAXPROCS to 1
> before tests start.
>
> perhaps this is a scheduler bug than a test bug.
>
Want to take a look? It was failing with 1.2 allocations per test instead
of the expected 1.0.
Russ
On Thu, Mar 7, 2013 at 10:18 PM, Russ Cox <rsc@golang.org> wrote: > Want to ...
12 years, 8 months ago
(2013-03-07 14:44:12 UTC)
#10
On Thu, Mar 7, 2013 at 10:18 PM, Russ Cox <rsc@golang.org> wrote:
> Want to take a look? It was failing with 1.2 allocations per test instead of
> the expected 1.0.
I'm still tackling the cgo problems on arm,
so i filed https://code.google.com/p/go/issues/detail?id=5000 to remind us.
Note:
from the original issue report, fullung said that the allocation comes from
runtime, so we should do something or this problem might affect other
Go 1 allocation tests in the wild that adopt the idiom:
defer runtime.GOMAXPROCS(runtime.GOMAXPROCS(1))
before tests.
Issue 7545043: code review 7545043: fmt: Skip TestCountMallocs if GOMAXPROCS>1.
(Closed)
Created 12 years, 8 months ago by albert.strasheim
Modified 12 years, 8 months ago
Reviewers: minux1
Base URL:
Comments: 0