Here is an example build failure when run from some other package:
$ go test pathing
../pathing/pathing_test.go:13: undefined: name
FAIL pathing [build failed]
The way go test failures are reported makes it difficult for tooling that processes compilation/test output (emacs electric compilation buffers) to locate the reported file. The errors that come from the build phase are relative paths; the ones coming from test are filenames-only.
Test failures should include path to the file-under-test.
The text was updated successfully, but these errors were encountered:
I think that ship has sailed. I don't see how to do that without breaking lots of people. Also, the reason the compiler errors can do that is that the go command arranges to get the entire path and then rewrites the printed absolute paths to be relative to the current directory.
Unlike the compiler, test binaries are frequently run separate from the go command, so this trick does not work. Test binaries are also copied to other machines and so on. Users also expect the current output, because that's what has been there for a long time. For all these reasons I think we can't change this. Sorry.