What version of Go are you using (go version)?

$ go version
go version devel go1.19-4e79f06dac Fri May 6 22:04:35 2022 +0000 linux/amd64

Does this issue reproduce with the latest release?

Yes. It's been around for a couple of releases.

What operating system and processor architecture are you using (go env)?

linux/amd64

What did you do?

$ cd `go env GOROOT`/src/internal/cpu
$ go test -cover

What did you expect to see?

Passing test with coverage:

PASS
coverage: 41.7% of statements
ok  	internal/cpu	0.034s
thanm@cetina:/ssd2/go/src/internal/cpu$ 

What did you see instead?

$ go test -cover
--- FAIL: TestDisableAllCapabilities (0.01s)
    cpu_test.go:44: TestAllCapabilitiesDisabled with GODEBUG=cpu.all=off: want PASS, got statements
--- FAIL: TestDisableSSE3 (0.01s)
    cpu_test.go:44: TestSSE3DebugOption with GODEBUG=cpu.sse3=off: want PASS, got statements
FAIL
coverage: 41.7% of statements
exit status 1
FAIL	internal/cpu	0.036s
$

What's happening here is that the test is invoking itself (cmd.Exec on os.Argv[0]) and then expecting to see a single "PASS" result instead of PASS + code coverage.