Closed
Description
--- FAIL: TestScript (0.01s)
--- FAIL: TestScript/test_fuzz_mutate_crash (88.46s)
script_test.go:260:
# Tests that a crash caused by a mutator-discovered input writes the bad input
# to testdata, and fails+reports correctly. This tests the end-to-end behavior
# of the mutator finding a crash while fuzzing, adding it as a regression test
# to the seed corpus in testdata, and failing the next time the test is run. (0.000s)
# Running the seed corpus for all of the targets should pass the first
# time, since nothing in the seed corpus will cause a crash. (2.332s)
# Running the fuzzer should find a crashing input quickly. (12.085s)
# Now, the failing bytes should have been added to the seed corpus for
# the target, and should fail when run without fuzzing. (62.971s)
# Running the fuzzer should find a crashing input quickly for fuzzing two types. (2.694s)
# Running the fuzzer should find a crashing input quickly for an integer. (4.696s)
# Running the fuzzer should find a crashing input quickly for a bool. (2.045s)
# Running the fuzzer should find a crashing input quickly for a float. (1.497s)
> ! go test -run=FuzzFloat -fuzz=FuzzFloat -fuzztime=100x -fuzzminimizetime=1000x
[stdout]
warning: starting with empty corpus
fuzz: elapsed: 0s, execs: 0 (0/sec), new interesting: 0 (total: 0)
fuzz: elapsed: 0s, execs: 100 (806/sec), new interesting: 1 (total: 1)
PASS
ok m 0.271s
FAIL: testdata\script\test_fuzz_mutate_crash.txt:89: unexpected command success
FAIL
FAIL cmd/go 210.036s
greplogs -l -e 'FAIL: TestScript/test_fuzz_mutate_crash .*(\n\s+.*)* unexpected command success'
2022-05-10T19:40:04-526de61/windows-amd64-longtest
(attn @golang/fuzzing)
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
No status