aboutsummaryrefslogtreecommitdiff
path: root/src/cmd/internal/test2json/testdata/unicode.json
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2017-11-09 19:54:42 -0500
committerRuss Cox <rsc@golang.org>2017-11-10 13:53:15 +0000
commit7badae85f20f1bce4cc344f9202447618d45d414 (patch)
treeca6bc51d95d69b0153bb958692d450d69434190e /src/cmd/internal/test2json/testdata/unicode.json
parent3231d4e4ef37df9c4457c1ce1ae3f46cf4b994f7 (diff)
downloadgo-7badae85f20f1bce4cc344f9202447618d45d414.tar.xz
cmd/go: guarantee all test output is on stdout
In past releases, whether test output appears on stdout or stderr has varied depending on exactly how go test was invoked and also (indefensibly) on the number of CPUs available. Standardize on standard output for all test output. This is easy to explain and makes go test | go tool test2json work nicely. Change-Id: I605641213fbc6c7ff49e1fd38a0f732045a8383d Reviewed-on: https://go-review.googlesource.com/76871 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Diffstat (limited to 'src/cmd/internal/test2json/testdata/unicode.json')
0 files changed, 0 insertions, 0 deletions