mirror of https://github.com/golang/go.git
7b88715882
The -test.v=test2json flag causes the testing package to inject extra control characters in the output to allow the JSON parser to more gracefully handle extraneous writes to os.Stdout and/or os.Stderr in the package under test (see CL 443596). However, it doesn't filter out those control characters because almost no real-world tests will output them. It turns out that testing.TestFlag is one of the rare tests that does output those control characters, because it tests the -test.v=test2json flag itself. Fixes #59181. Change-Id: I35ca6748afcd3d4333563028817caac946f5e86a Reviewed-on: https://go-review.googlesource.com/c/go/+/479035 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> |
||
|---|---|---|
| .. | ||
| fstest | ||
| internal/testdeps | ||
| iotest | ||
| quick | ||
| allocs.go | ||
| allocs_test.go | ||
| benchmark.go | ||
| benchmark_test.go | ||
| cover.go | ||
| example.go | ||
| export_test.go | ||
| flag_test.go | ||
| fuzz.go | ||
| helper_test.go | ||
| helperfuncs_test.go | ||
| match.go | ||
| match_test.go | ||
| newcover.go | ||
| panic_test.go | ||
| run_example.go | ||
| run_example_js.go | ||
| sub_test.go | ||
| testing.go | ||
| testing_other.go | ||
| testing_test.go | ||
| testing_windows.go | ||