1
0
mirror of https://github.com/golang/go synced 2024-11-16 20:54:48 -07:00

cmd/go: add space after comma in 'go help test'

This PR fixes a simple typo. It adds a space after a comma. Noticed while looking at `go help test` output.

Change-Id: I5b54f4da0d08a056bffc04899983d858dfa91043
GitHub-Last-Rev: da9cab5eb9
GitHub-Pull-Request: golang/go#53931
Reviewed-on: https://go-review.googlesource.com/c/go/+/418034
Reviewed-by: Bryan Mills <bcmills@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Auto-Submit: Bryan Mills <bcmills@google.com>
Run-TryBot: Bryan Mills <bcmills@google.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>
This commit is contained in:
Justin Traglia 2022-07-20 14:20:41 +00:00 committed by Gopher Robot
parent 9eb3992ddd
commit 795a88d0c3
2 changed files with 2 additions and 2 deletions

View File

@ -1708,7 +1708,7 @@
// the package's source root (usually $GOPATH) or that consult environment // the package's source root (usually $GOPATH) or that consult environment
// variables only match future runs in which the files and environment // variables only match future runs in which the files and environment
// variables are unchanged. A cached test result is treated as executing // variables are unchanged. A cached test result is treated as executing
// in no time at all,so a successful package test result will be cached and // in no time at all, so a successful package test result will be cached and
// reused regardless of -timeout setting. // reused regardless of -timeout setting.
// //
// In addition to the build flags, the flags handled by 'go test' itself are: // In addition to the build flags, the flags handled by 'go test' itself are:

View File

@ -132,7 +132,7 @@ test caching explicitly is to use -count=1. Tests that open files within
the package's source root (usually $GOPATH) or that consult environment the package's source root (usually $GOPATH) or that consult environment
variables only match future runs in which the files and environment variables only match future runs in which the files and environment
variables are unchanged. A cached test result is treated as executing variables are unchanged. A cached test result is treated as executing
in no time at all,so a successful package test result will be cached and in no time at all, so a successful package test result will be cached and
reused regardless of -timeout setting. reused regardless of -timeout setting.
In addition to the build flags, the flags handled by 'go test' itself are: In addition to the build flags, the flags handled by 'go test' itself are: