Join GitHub today
cmd/go: document exit codes of a process executing `go test` #25989
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
Do we distinguish between flag parsing errors where different exit codes are output? For example, passing in "-c=invalid" returns a 2
while passing in "-covermode=invalid" returns a 1.
@GTB3NW note that your particular problem is most possibly not related to the essense of this issue which is about documenting the implemented behaviour which appears to be OK.
I've created this issue merely because such things ought to be documented for reference purposes (say, for DevOps folks which may be not too familiar with Go to implement the CI pipeline).
Try to figure out what may mask the exit code of your
this code won't ever exit if
Updated @GTB3NW, ah, I see you got sorted it out :-)
Okay here's one for you then, I've read the documentation, perhaps I'm missing something here, but the following should FAIL and return error code 1 should it not?
Should that not be a FAIL on /blahtest too?
The aim is to just run:
Test all the packages and if any one of them fails the whole test fails, surely that's a common requirement. Either I'm misunderstanding the testing facilities/there's a bug/go test is lacking something critical.
Could anyone set me in the right direction please I'd really appreciate it :)