cmd/go: do not expect a specific timing in test_fuzz_minimize

Empirically, it may take more than 3 seconds for minimization to begin.
If that is the case, the "elapsed:" message may start at 4s or higher.

Fixes #48870

Change-Id: I6bb4367b61377454b0af664d80232fdb46e7c245
Reviewed-on: https://go-review.googlesource.com/c/go/+/354794
Trust: Bryan C. Mills <bcmills@google.com>
Run-TryBot: Bryan C. Mills <bcmills@google.com>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Jay Conrod <jayconrod@google.com>

diff --git a/src/cmd/go/testdata/script/test_fuzz_minimize.txt b/src/cmd/go/testdata/script/test_fuzz_minimize.txt
index 727399f4bbf9d6aa6671152ac53c41f902ea4868..0a0359fabb8431597b5c4c94ef2f6d7a16d6c260 100644 (file)
--- a/src/cmd/go/testdata/script/test_fuzz_minimize.txt
+++ b/src/cmd/go/testdata/script/test_fuzz_minimize.txt
@@ -76,7 +76,7 @@ stdout FAIL
 
 ! go test -fuzz=FuzzMinimizerTooSlow -run=FuzzMinimizerTooSlow -fuzzminimizetime=3s minimizer_test.go
 stdout 'fuzz: minimizing'
-stdout 'fuzz: elapsed: 3s, minimizing'
+stdout 'fuzz: elapsed: \d+s, minimizing'
 stdout 'testdata[/\\]fuzz[/\\]FuzzMinimizerTooSlow[/\\]'
 stdout FAIL