Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Copied from a comment I left on https://golang.org/cl/76872 after it was merged.)
I tried using the new test2json tool and found it initially confusing. Here it says
// Usage: // // go test ... | go tool test2json [-p pkg] [-t] // ./test.out 2>&1 | go tool test2json [-p pkg] [-t]
Should that recommend go test -v? Without -v, it says the test failed even when it passed:
go test -v
-v
$ go test strings | go tool test2json {"Action":"output","Output":"ok \tstrings\t(cached)\n"} {"Action":"fail"}
cc @rsc
The text was updated successfully, but these errors were encountered:
Change https://golang.org/cl/81555 mentions this issue: cmd/test2json: add ability to run test binary
cmd/test2json: add ability to run test binary
Sorry, something went wrong.
7684fe0
No branches or pull requests
(Copied from a comment I left on https://golang.org/cl/76872 after it was merged.)
I tried using the new test2json tool and found it initially confusing. Here it says
Should that recommend
go test -v
? Without-v
, it says the test failed even when it passed:cc @rsc
The text was updated successfully, but these errors were encountered: