-
-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
race build does not respect race build tag #1559
Comments
Also: clean up the race tests, move to tests/core, and test that the race tag is set. Fixes bazel-contrib#1559
Thanks for reporting. This was overlooked functionality. #1562 will enable |
Also: clean up the race tests, move to tests/core, and test that the race tag is set. Fixes #1559
…b#1562) Also: clean up the race tests, move to tests/core, and test that the race tag is set. Fixes bazel-contrib#1559
After pulling this change into gvisor I am getting:
Is it that bazel is somehow confused by these complex expressions in build tags? |
Bazel is doing the right thing. The problem is that Gazelle is not including race.go in the |
I am trying to build gvisor in race more:
This will also require disabling pure mode for the binary, as it silently disables race more:
runsc/boot/filter/extra_filters_race.go
file contains race build tag// +build race
, but if I do:The build still passes. Which suggests that
--features=race
does not respect race tag.Both
--features=race
andrace = "on"
binary attribute need to respect race build tag.While we are here, it can make sense to do the same for msan and
--features=msan
, there is a similar filerunsc/boot/filter/extra_filters_msan.go
.The text was updated successfully, but these errors were encountered: