mirror of https://github.com/golang/go.git
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>
This commit is contained in:
parent
f47335e653
commit
8c94aa40e6
|
|
@ -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 @@ skip # Flaky: https://golang.org/issue/49046
|
|||
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
|
||||
|
|
|
|||
Loading…
Reference in New Issue