/ go Public
cmd/go: "go test" seems to cache test build output when GODEBUG changes #51561
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
I was using
GODEBUG=inittrace=1to get some quick stats on the init cost of some packages via
go test, and I noticed that even after I unset the variable, its output was still around - presumably via Go's cache.
As a repro:
It's unclear why the number of lines diminishes, but they're all still inittrace output.
go builddoes not show this bug, so presumably the bug is with the test cache:
Perhaps Go's cache should be taught to include
GODEBUGas part of cache key hashes.
The text was updated successfully, but these errors were encountered: