You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run go test ./..., the cache kicks in as expected:
% time CGO_ENABLED=0 go test ./...
ok formmailer/cmd/formmailer (cached)
CGO_ENABLED=0 go test ./... 2,64s user 1,02s system 561% cpu 0,651 total
But adding the -fullpath flag prevents caching:
% time CGO_ENABLED=0 go test -fullpath ./...
ok formmailer/cmd/formmailer 0.947s
CGO_ENABLED=0 go test -fullpath ./... 7,18s user 1,66s system 592% cpu 1,492 total
% time CGO_ENABLED=0 go test -fullpath ./...
ok formmailer/cmd/formmailer 0.924s
CGO_ENABLED=0 go test -fullpath ./... 7,60s user 1,69s system 620% cpu 1,496 total
go help test speaks of a restricted set of 'cacheable' test flags, defined as -benchtime, -cpu, -list, -parallel, -run, -short, -timeout, -failfast, and -v.
It seems to me like we should add -fullpath to the list of cacheable test flags.
What did you expect to see?
Caching should work even when using -fullpath
What did you see instead?
Caching did not work.
The text was updated successfully, but these errors were encountered:
Go version
go version go1.21.4 linux/amd64
What operating system and processor architecture are you using (
go env
)?What did you do?
When I run
go test ./...
, the cache kicks in as expected:But adding the
-fullpath
flag prevents caching:go help test
speaks ofa restricted set of 'cacheable' test flags, defined as -benchtime, -cpu, -list, -parallel, -run, -short, -timeout, -failfast, and -v.
It seems to me like we should add
-fullpath
to the list of cacheable test flags.What did you expect to see?
Caching should work even when using -fullpath
What did you see instead?
Caching did not work.
The text was updated successfully, but these errors were encountered: