goos: linux
goarch: amd64
pkg: example.com/nop/issue
cpu: Intel(R) Xeon(R) W-2135 CPU @ 3.70GHz
BenchmarkA
BenchmarkA-12               1074           1114089 ns/op
BenchmarkA-12               1059           1116605 ns/op
BenchmarkA-12               1069           1116068 ns/op
BenchmarkA-12               1082           1109577 ns/op
BenchmarkA-12               1092           1114838 ns/op
BenchmarkA-12               1057           1127497 ns/op
BenchmarkA-12               1068           1112353 ns/op
BenchmarkA-12               1082           1119847 ns/op
BenchmarkA-12               1069           1109970 ns/op
BenchmarkA-12               1076           1119566 ns/op
BenchmarkB
BenchmarkB-12               1086           1115953 ns/op
BenchmarkB-12               1054           1115512 ns/op
BenchmarkB-12               1120           1111781 ns/op
BenchmarkB-12               1080           1122841 ns/op
BenchmarkB-12               1081           1110178 ns/op
BenchmarkB-12               1069           1116808 ns/op
BenchmarkB-12               1068           1110374 ns/op
BenchmarkB-12               1072           1119656 ns/op
BenchmarkB-12               1058           1102025 ns/op
BenchmarkB-12               1108           1082698 ns/op
PASS
ok      example.com/nop/issue   26.259s

The second, called package list mode, occurs when go test is invoked
with explicit package arguments (for example 'go test math', 'go
test ./...', and even 'go test .'). In this mode, go test compiles
and tests each of the packages listed on the command line. If a
package test passes, go test prints only the final 'ok' summary
line. If a package test fails, go test prints the full test output.
If invoked with the -bench or -v flag, go test prints the full
output even for passing package tests, in order to display the
requested benchmark results or verbose logging. After the package
tests for all of the listed packages finish, and their output is
printed, go test prints a final 'FAIL' status if any package test
has failed.