@@ -119,14 +119,14 @@ elapsed time in the summary line.
119
119
The rule for a match in the cache is that the run involves the same
120
120
test binary and the flags on the command line come entirely from a
121
121
restricted set of 'cacheable' test flags, defined as -benchtime, -cpu,
122
- -list, -parallel, -run, -short, -timeout, -failfast, and -v.
123
- If a run of go test has any test or non-test flags outside this set,
124
- the result is not cached. To disable test caching, use any test flag
122
+ -list, -parallel, -run, -short, -timeout, -failfast, and -v.
123
+ If a run of go test has any test or non-test flags outside this set,
124
+ the result is not cached. To disable test caching, use any test flag
125
125
or argument other than the cacheable flags. The idiomatic way to disable
126
126
test caching explicitly is to use -count=1. Tests that open files within
127
- the package's source root (usually $GOPATH) or that consult environment
127
+ the package's source root (usually $GOPATH) or that consult environment
128
128
variables only match future runs in which the files and environment
129
- variables are unchanged. A cached test result is treated as executing
129
+ variables are unchanged. A cached test result is treated as executing
130
130
in no time at all,so a successful package test result will be cached and
131
131
reused regardless of -timeout setting.
132
132
0 commit comments