qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-23 06:40:05 -07:00
Code Releases Activity

fix:delete trailing whitespace

Browse Source
This commit is contained in:
kezhao 2021-07-28 10:03:14 +08:00
parent 1b7e32d480
commit abe61fd48c
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/cmd/go/internal/test/test.go
View File

@ -119,14 +119,14 @@ elapsed time in the summary line.
The rule for a match in the cache is that the run involves the same The rule for a match in the cache is that the run involves the same
test binary and the flags on the command line come entirely from a test binary and the flags on the command line come entirely from a
restricted set of 'cacheable' test flags, defined as -benchtime, -cpu, restricted set of 'cacheable' test flags, defined as -benchtime, -cpu,
-list, -parallel, -run, -short, -timeout, -failfast, and -v. -list, -parallel, -run, -short, -timeout, -failfast, and -v.
If a run of go test has any test or non-test flags outside this set, If a run of go test has any test or non-test flags outside this set,
the result is not cached. To disable test caching, use any test flag the result is not cached. To disable test caching, use any test flag
or argument other than the cacheable flags. The idiomatic way to disable or argument other than the cacheable flags. The idiomatic way to disable
test caching explicitly is to use -count=1. Tests that open files within 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.