-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: go clean -testcache fails if GOCACHE directory does not exist #29100
Comments
/cc @bcmills |
I believe this was fixed by #28680. Please reopen if you can still reproduce it at head.
|
The issue does not seem to be fixed. Running version:
Gives the following error message:
|
Yes, I can recreate this if I rename the entire cache directory as the first comment suggests. |
Trying to find a possible regression, related to issued: golang/go#29100
Trying to find a possible regression, related to issued: golang/go#29100
Trying to find a possible regression, related to issued: golang/go#29100
Trying to find a possible regression, related to issued: golang/go#29100
Trying to find a possible regression, related to issued: golang/go#29100
I can work on this. I would like to confirm something. Is it, no fail and no warning, the expected behavior? Is it a correct assumption that is there is no |
@jespino, I think the error comes from here: go/src/cmd/go/internal/clean/clean.go Line 164 in 6145a80
(Actually, that makes the fix pretty trivial — simpler to mail a fix than to explain it here.) |
Change https://golang.org/cl/212099 mentions this issue: |
With the release of go 1.4 the following issue got closed: - golang/go#29100
Moving to new golang version since the following issue got fixed: - golang/go#29100
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes. It may be affected by #26794 for 1.12, but looking at the code, I think the bug is still there.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
No errors and an exit code of 0.
What did you see instead?
The
-testcache
flag assumes that the cache directory exists. When that's not the case, there is nothing to clear, so the command should exit normally.The text was updated successfully, but these errors were encountered: