From f368abb46e15419c95d3f5933e9344476e1efc2a Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Thu, 8 Dec 2022 12:53:26 -0500 Subject: doc/go1.20: correct test binary -v flag value for test2json The -v flag value is "test2json", not "json", since it emits output in a custom format that the cmd/test2json tool interprets. The cmd/test2json documentation and implementation have this right. For #54202. Change-Id: I2b52861d926e14488aa9fc89fff8c26da32ca710 Reviewed-on: https://go-review.googlesource.com/c/go/+/456124 Reviewed-by: Bryan Mills Auto-Submit: Dmitri Shuralyov TryBot-Result: Gopher Robot Run-TryBot: Dmitri Shuralyov Reviewed-by: Dmitri Shuralyov --- doc/go1.20.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/go1.20.html b/doc/go1.20.html index 28d3c8224d..e479fce8a1 100644 --- a/doc/go1.20.html +++ b/doc/go1.20.html @@ -102,9 +102,9 @@ Do not send CLs removing the interior tags from such phrases. Programs that run go test -json do not need any updates. Programs that invoke go tool test2json - directly should now run the test binary with -v=json - (for example, go test -v=json - or ./pkg.test -test.v=json) + directly should now run the test binary with -v=test2json + (for example, go test -v=test2json + or ./pkg.test -test.v=test2json) instead of plain -v.

-- cgit v1.2.1