-
Notifications
You must be signed in to change notification settings - Fork 18.8k
Closed
Labels
FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.fuzzIssues related to native fuzzing supportIssues related to native fuzzing supportrelease-blocker
Milestone
Description
While testing locally, I noticed that -fuzzminimizetime doesn't work when running with something like 10x.
Even when -fuzzminimizetime is set to 10x, it runs many more times than that.
godev test -run Fuzz -fuzz Fuzz -fuzzminimizetime=10x
fuzz: elapsed: 0s, gathering baseline coverage: 0/25 completed
fuzz: elapsed: 0s, gathering baseline coverage: 25/25 completed, now fuzzing with 8 workers
fuzz: minimizing 1474-byte crash input...
fuzz: elapsed: 0s, minimizing
--- FAIL: FuzzFuzzer (0.15s)
--- FAIL: FuzzFuzzer (0.00s)
dsa_test.go:19: minimize this! 0, len(s)=478
--- FAIL: FuzzFuzzer (0.00s)
dsa_test.go:19: minimize this! 0, len(s)=478
.... this goes on for a while
--- FAIL: FuzzFuzzer (0.00s)
dsa_test.go:19: minimize this! 0, len(s)=4
--- FAIL: FuzzFuzzer (0.00s)
dsa_test.go:19: minimize this! 0, len(s)=3
--- FAIL: FuzzFuzzer (0.00s)
dsa_test.go:19: minimize this! 0, len(s)=2
--- FAIL: FuzzFuzzer (0.00s)
dsa_test.go:19: minimize this! 0, len(s)=1
Crash written to testdata/fuzz/FuzzFuzzer/d8398164056fc45958535f08a1b29a7fd10a21f12c95b34d4b891c6f9842b6d3
To re-run:
go test foo -run=FuzzFuzzer/d8398164056fc45958535f08a1b29a7fd10a21f12c95b34d4b891c6f9842b6d3
FAIL
exit status 1
FAIL foo 0.317s
/cc @golang/fuzzing
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.fuzzIssues related to native fuzzing supportIssues related to native fuzzing supportrelease-blocker
Type
Projects
Status
No status