language: use multiple runs in TestBestMatchAlloc
AllocsPerRun sets runtime.GOMAXPROCS to 1, but it doesn't prevent the runtime from descheduling a goroutine
and performing an allocation somewhere in the background.
This commit changes the test to use a number of runs large enough to average away the occasional noisy allocation.
Fixes golang/go#45809
Change-Id: Ibf904016d0c067740469c8e861079611440222a1
GitHub-Last-Rev: 1606b6969a4d462804dda8d98b9c4432241e87ea
GitHub-Pull-Request: golang/text#23
Reviewed-on: https://go-review.googlesource.com/c/text/+/321737
Reviewed-by: Bryan C. Mills <bcmills@google.com>
Trust: Michael Knyszek <mknyszek@google.com>
diff --git a/language/match_test.go b/language/match_test.go
index a6df3e1..313580b 100644
--- a/language/match_test.go
+++ b/language/match_test.go
@@ -242,7 +242,7 @@
m := NewMatcher(makeTagList("en sr nl"))
// Go allocates when creating a list of tags from a single tag!
list := []Tag{English}
- avg := testtext.AllocsPerRun(1, func() {
+ avg := testtext.AllocsPerRun(100, func() {
m.Match(list...)
})
if avg > 0 {
