From 7fcf9a1e58c088eb63b7fc3db494016bf210966b Mon Sep 17 00:00:00 2001 From: "Bryan C. Mills" Date: Fri, 8 Oct 2021 14:12:33 -0400 Subject: [PATCH] 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 Run-TryBot: Bryan C. Mills TryBot-Result: Go Bot Reviewed-by: Jay Conrod --- src/cmd/go/testdata/script/test_fuzz_minimize.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cmd/go/testdata/script/test_fuzz_minimize.txt b/src/cmd/go/testdata/script/test_fuzz_minimize.txt index 727399f4bb..0a0359fabb 100644 --- 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 -- 2.50.0