commit 8c94aa40e6f5e61e8a570e9d20b7d0d4ad8c382d
author Katie Hockman <katie@golang.org> Fri Oct 22 11:56:23 2021 -0400
committer Katie Hockman <katie@golang.org> Mon Oct 25 18:59:26 2021 +0000
tree 1b50291ba11ba6e7fc13e9bb7080db392b098277
parent f47335e653ac37f68ada2b265ce4a2c869a27cae

cmd/go/testdata/script: fix flaky test_fuzz_fuzztime test

Previously, the test would panic if the short timeout
was reached before fuzzing began. Increasing the
timeout should stop this test from being flaky.

Fixes #49046

Change-Id: Iaa0b3b3e8ea29d9a42ab5fc1c801fc73fffe1675
Reviewed-on: https://go-review.googlesource.com/c/go/+/358055
Trust: Katie Hockman <katie@golang.org>
Run-TryBot: Katie Hockman <katie@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Bryan C. Mills <bcmills@google.com>

src/cmd/go/testdata/script/test_fuzz_fuzztime.txt

diff --git a/src/cmd/go/testdata/script/test_fuzz_fuzztime.txt b/src/cmd/go/testdata/script/test_fuzz_fuzztime.txt
index 6264aca..c3933bc 100644
--- a/src/cmd/go/testdata/script/test_fuzz_fuzztime.txt
+++ b/src/cmd/go/testdata/script/test_fuzz_fuzztime.txt
@@ -1,5 +1,3 @@
-skip  # Flaky: https://golang.org/issue/49046
-
 # TODO(jayconrod): support shared memory on more platforms.
 [!darwin] [!linux] [!windows] skip
 
@@ -9,11 +7,11 @@
 go test
 
 # Fuzzing should exit 0 after fuzztime, even if timeout is short.
-go test -timeout=10ms -fuzz=FuzzFast -fuzztime=5s
+go test -timeout=3s -fuzz=FuzzFast -fuzztime=5s
 
 # We should see the same behavior when invoking the test binary directly.
 go test -c
-exec ./fuzz.test$GOEXE -test.timeout=10ms -test.fuzz=FuzzFast -test.fuzztime=5s -test.parallel=1 -test.fuzzcachedir=$WORK/cache
+exec ./fuzz.test$GOEXE -test.timeout=3s -test.fuzz=FuzzFast -test.fuzztime=5s -test.parallel=1 -test.fuzzcachedir=$WORK/cache
 
 # Timeout should not cause inputs to be written as crashers.
 ! exists testdata/fuzz