Commit 9719ca9c authored by Dmitri Shuralyov's avatar Dmitri Shuralyov Committed by Rob Pike

cmd/go: fix two formatting issues in documentation of testing flags

Remove unneeded second colon.

Remove unneeded space at the beginning of a line (before a tab).

Regenerate alldocs.go with mkalldocs.sh.

Updates https://golang.org/cl/28783.
Updates https://golang.org/cl/29650.
Fixes #18448.

Change-Id: I1830136a2b760827d4cec565744807a0fd147584
Reviewed-on: https://go-review.googlesource.com/34718Reviewed-by: default avatarRob Pike <r@golang.org>
parent 5bfba30d
......@@ -1474,7 +1474,7 @@
// text from Log and Logf calls even if the test succeeds.
//
// The following flags are also recognized by 'go test' and can be used to
// profile the tests during execution::
// profile the tests during execution:
//
// -benchmem
// Print memory allocation statistics for benchmarks.
......@@ -1517,7 +1517,7 @@
// Writes test binary as -c would.
//
// -mutexprofilefraction n
// Sample 1 in n stack traces of goroutines holding a
// Sample 1 in n stack traces of goroutines holding a
// contended mutex.
//
// -outputdir directory
......
......@@ -200,7 +200,7 @@ const testFlag2 = `
text from Log and Logf calls even if the test succeeds.
The following flags are also recognized by 'go test' and can be used to
profile the tests during execution::
profile the tests during execution:
-benchmem
Print memory allocation statistics for benchmarks.
......@@ -243,7 +243,7 @@ profile the tests during execution::
Writes test binary as -c would.
-mutexprofilefraction n
Sample 1 in n stack traces of goroutines holding a
Sample 1 in n stack traces of goroutines holding a
contended mutex.
-outputdir directory
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment