mirror of
https://github.com/golang/go
synced 2024-11-19 03:14:42 -07:00
testing: unflake TestBRun
by only testing the lower bound of memalloc Fixes #15063 Change-Id: Iab2fdd75e9ce98c641bfbce57f142fa47176772d Reviewed-on: https://go-review.googlesource.com/21507 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Marcel van Lohuizen <mpvl@golang.org>
This commit is contained in:
parent
060501dc0e
commit
8bc9c57b18
@ -384,10 +384,14 @@ func TestBRun(t *T) {
|
||||
}
|
||||
b.Run("", func(b *B) { alloc(b) })
|
||||
b.Run("", func(b *B) { alloc(b) })
|
||||
if got := b.result.MemAllocs; got != 2 {
|
||||
// runtime.MemStats sometimes reports more allocations than the
|
||||
// benchmark is responsible for. Luckily the point of this test is
|
||||
// to ensure that the results are not underreported, so we can
|
||||
// simply verify the lower bound.
|
||||
if got := b.result.MemAllocs; got < 2 {
|
||||
t.Errorf("MemAllocs was %v; want 2", got)
|
||||
}
|
||||
if got := b.result.MemBytes; got != 2*bufSize {
|
||||
if got := b.result.MemBytes; got < 2*bufSize {
|
||||
t.Errorf("MemBytes was %v; want %v", got, 2*bufSize)
|
||||
}
|
||||
},
|
||||
|
Loading…
Reference in New Issue
Block a user