]> Cypherpunks repositories - gostls13.git/commit
internal/fuzz: don't use dirty coverage maps during minimization
authorRoland Shoemaker <roland@golang.org>
Thu, 10 Mar 2022 20:16:33 +0000 (12:16 -0800)
committerGopher Robot <gobot@golang.org>
Thu, 10 Mar 2022 22:50:18 +0000 (22:50 +0000)
commitbd71dee2b4c0a44f9c32e9eb23d990b54ce06bae
tree898203a0c9305174cf18baf57e90a9d2fd8592c5
parent914195c132cbec651aa43c409e8aac2614b53b38
internal/fuzz: don't use dirty coverage maps during minimization

When minimizing a value, if the value cannot be minimized (i.e. it is
the final value is the same value as was sent for minimization) return
the initial coverage map, rather than the coverageSnapshot, which is
actually the coverage map for the final minimization step and may not
accurately reflect whether the input actually expands the coverage set
or not.

Updates #48326

Change-Id: I01f0eebe5841e808b6799647d2e5fe3aa45cd2e0
Reviewed-on: https://go-review.googlesource.com/c/go/+/391614
Reviewed-by: Bryan Mills <bcmills@google.com>
Trust: Roland Shoemaker <roland@golang.org>
Run-TryBot: Roland Shoemaker <roland@golang.org>
Auto-Submit: Roland Shoemaker <roland@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
src/cmd/go/testdata/script/test_fuzz_minimize_dirty_cov.txt [new file with mode: 0644]
src/internal/fuzz/worker.go