Closed
Description
When run with GOPATH=/dev/null
, go build
fails:
$ GOPATH=/dev/null go test -run=TestLldbPython -v -count=1 runtime
=== RUN TestLldbPython
--- FAIL: TestLldbPython (0.21s)
runtime-lldb_test.go:169: building source exit status 1
go: failed to create cache directory /dev/null/pkg/mod/cache: mkdir /dev/null: not a directory
FAIL
FAIL runtime 0.220s
That seems fine. Who would run with GOPATH=/dev/null
‽ It's not even a directory.
But it's not fine, because run.bash sets GOPATH=/dev/null
. Why? The comment says: The $GOPATH value doesn't need to point to an actual directory, it just needs to pass the semantic checks performed by Go.
I don't know who is wrong here, but I do want all.bash to pass. I have a workaround I can mail just for TestLldbPython (set GOPATH=
). Or we can fix this mess...somewhere else.
Opinions?