-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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: error if GOCACHE is set but is not an absolute path #30447
Comments
Don't set |
Thanks, I was wondering why the hell the tmp directory is named "on". 😂 I have an explanation for this. The story goes that I had this settings on "off", but 1.12 didn't want to compile with GOCACHE="off". I try to delete it from .bash_profile but VSCode haven't picked up that change after several VSCode restarts, so I put it back and set it to "on". Compile started to work and I end up with "on/" directory for cache files 😂 but |
Also see previous conversation here #28290. |
Change https://golang.org/cl/164200 mentions this issue: |
Now when I know for this issue, I don't mind if it will be relative or absolute path. The off value is history now, so I guess I will never use this env var ever again. But for transition period like now when I upgraded from 1.11 to 1.12 and moved from "off" to "on" 😆 warning on abs path would save me a lot of wasted time. :) |
Does anyone know how can I avoid cache in
|
https://golang.org/cmd/go/#hdr-Test_packages
|
@gopherbot please backport to 1.12 |
Backport issue(s) opened: #30493 (for 1.12). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Test running
What did you see instead?
Build error and test failed probably due to new structure for cache directories in 1.12
Executing
go clean -cache
will fix a problem for a while, but then it starts occurring again.The text was updated successfully, but these errors were encountered: