1 # Adding -cover to "go test -n" should not cause failures,
2 # see issue 67952. In the regular (no "-n") case for an
3 # empty package test action for the package will look for
4 # a static meta-data file produced by the cover tool
5 # during the build action; when "-n" is in effect that
6 # meta-data file doesn't exist, so the code that reads
7 # the meta-data file has to be stubbed out.
8
9 go test -vet=off -n -cover ./f
10
11 -- go.mod --
12 module M
13
14 go 1.21
15 -- f/f.go --
16 package f
17
18 func Id() int {
19 return 42
20 }
21
View as plain text