Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go/internal/cache: build cache's README file is not accurate #48900

Open
AlekSi opened this issue Oct 10, 2021 · 3 comments
Open

cmd/go/internal/cache: build cache's README file is not accurate #48900

AlekSi opened this issue Oct 10, 2021 · 3 comments

Comments

@AlekSi
Copy link
Contributor

@AlekSi AlekSi commented Oct 10, 2021

What did you do?

cat $(go env GOCACHE)/README

What did you see?

This directory holds cached build artifacts from the Go build system.
Run "go clean -cache" if the directory is getting too large.
See golang.org to learn more about Go.

What did you expect?

Given that go clean -cache does not clean $GOCACHE/fuzz, running that command might not be enough. Either that README should be updated to mention go clean -fuzzcache, or a new README file should be created in the fuzz subdirectory.

/cc @katiehockman @jayconrod

@AlekSi

This comment has been hidden.

@gopherbot gopherbot added the fuzz label Oct 10, 2021
@AlekSi AlekSi changed the title fuzzing: build cache's README file is not accurate cmd/go/internal/cache: build cache's README file is not accurate Oct 10, 2021
@bcmills bcmills added this to the Go1.18 milestone Oct 11, 2021
@emahiro
Copy link
Contributor

@emahiro emahiro commented Oct 21, 2021

Hi I committed about this issue in https://go-review.googlesource.com/c/go/+/357233

@gopherbot
Copy link

@gopherbot gopherbot commented Oct 21, 2021

Change https://golang.org/cl/357233 mentions this issue: internal/cache: add go clean -fuzzcache``

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants