You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ bazel coverage --@io_bazel_rules_go//go/config:race //foobar:all
...
//foobar:foobar_test PASSED in 0.1s
.../bazel-out/k8-fastbuild/testlogs/foobar/foobar_test/coverage.dat
Executed 1 out of 1 test: 1 test passes.
$ cat .../bazel-out/k8-fastbuild/testlogs/foobar/foobar_test/coverage.dat
mode: atomic
github.mpi-internal.com/leboncoin/go/foobar/foobar.go:3.12,5.2 1 1
What did you see instead?
$ cat .../bazel-out/k8-fastbuild/testlogs/foobar/foobar_test/coverage.dat
mode: set
github.mpi-internal.com/leboncoin/go/foobar/foobar.go:3.12,5.2 1 1
The cover mode in the coverage data file should be atomic, according with the argument given of the cover command of the builder. Since #2502 the coverage data is collected with the mode atomic when the race detection is enabled.
The coverage data file should specify the correct mode. It's necessary to merge all report data files with the correct aggregation function.
The text was updated successfully, but these errors were encountered:
What version of rules_go are you using?
v0.29.0
What version of gazelle are you using?
v0.24.0
What version of Bazel are you using?
v4.2.1
Does this issue reproduce with the latest releases of all the above?
Yes. This issue is reproduced with the HEAD of the master branch of rules_go (aaf48cb, 2021/11/12).
No direct correlation with Gazelle and Bazel.
What operating system and processor architecture are you using?
Linux / amd64
Any other potentially useful information about your toolchain?
Tested with local Go toolchain, and 1.17.3 Go toolchain.
What did you do?
Run coverage of a minimal Go test with -race mode.
foobar/foobar.go
:foobar/foobar_test.go
:foobar/BUILD.bazel
:And execute the command:
What did you expect to see?
What did you see instead?
The cover mode in the coverage data file should be atomic, according with the argument given of the cover command of the builder. Since #2502 the coverage data is collected with the mode atomic when the race detection is enabled.
The coverage data file should specify the correct mode. It's necessary to merge all report data files with the correct aggregation function.
The text was updated successfully, but these errors were encountered: