aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKatie Hockman <katie@golang.org>2021-02-23 12:06:29 -0500
committerKatie Hockman <katie@golang.org>2021-02-23 17:32:44 +0000
commit145e09d2b450a25e4d0672653ce06683a513cf94 (patch)
tree8663f2892f281a8e82dc519390c7b2fa36b2d1eb
parentc47ce694f67238188e2c2447932d83562ca3f148 (diff)
downloadgo-x-proposal-145e09d2b450a25e4d0672653ce06683a513cf94.tar.xz
design/draft-fuzzing.md: describe `go clean -fuzzcache`
Change-Id: Iaec8b8c9ee62bd348ec0bb7dd5303c859b0652de Reviewed-on: https://go-review.googlesource.com/c/proposal/+/295490 Trust: Katie Hockman <katie@golang.org> Run-TryBot: Katie Hockman <katie@golang.org> Reviewed-by: Jay Conrod <jayconrod@google.com>
-rw-r--r--design/draft-fuzzing.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/design/draft-fuzzing.md b/design/draft-fuzzing.md
index fe41717..19bf32f 100644
--- a/design/draft-fuzzing.md
+++ b/design/draft-fuzzing.md
@@ -480,6 +480,12 @@ The following flags will be added or have modified meaning:
`go test` will not respect `-p` when running with `-fuzz`, as it doesn't make
sense to fuzz multiple packages at the same time.
+There will also be a new flag, `-fuzzcache` introduced to `go clean`.
+When this flag is not set, `go clean` will not automatically remove generated
+corpus files, even though they are written into a subdirectory of `$GOCACHE`.
+In order to remove the generated corpus files, one must run
+`go clean -fuzzcache`, which will remove all generated corpus in `$GOCACHE`.
+
## Open questions and future work
### Fuzzing engine supports multiple targets at once