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

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

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

AlekSi opened this issue Oct 10, 2021 · 3 comments
Labels
Documentation FrozenDueToAge fuzz Issues related to native fuzzing support help wanted NeedsFix The path to resolution is known, but the work has not been done. okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 release-blocker
Milestone

Comments

@AlekSi
Copy link
Contributor

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 minimized.

@gopherbot gopherbot added the fuzz Issues related to native fuzzing support 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 Documentation NeedsFix The path to resolution is known, but the work has not been done. labels Oct 11, 2021
@bcmills bcmills added this to the Go1.18 milestone Oct 11, 2021
@katiehockman katiehockman added the okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 label Oct 20, 2021
@emahiro
Copy link
Contributor

emahiro commented Oct 21, 2021

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

@gopherbot
Copy link

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

@golang golang locked and limited conversation to collaborators Jun 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation FrozenDueToAge fuzz Issues related to native fuzzing support help wanted NeedsFix The path to resolution is known, but the work has not been done. okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 release-blocker
Projects
Status: No status
Development

No branches or pull requests

6 participants