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
test_tag_filter
should imply build_tag_filter
in bazel test
command
#8439
Comments
Does the flag |
Perhaps --test_tag_filters should imply use of build_tests_only. |
…unning `blaze test`. #8439 PiperOrigin-RevId: 325117049
…unning `blaze test`. bazelbuild#8439 PiperOrigin-RevId: 325117049
Another interesting related note is how |
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale. |
Description of the problem / feature request:
Right now, the somewhat innocent looking command
builds far more than it needs to to run the specified test.
As far as I can tell, this is because bazel is interpreting the
test
command asand since the first part of that ignores
--test_tag_filters
, the above innocent-looking command expands toThis is very counter-intuitive.
I suggest that the
build
part of abazel test
command use the same analysis as thetest
part of that command, so only the required test targets (and their dependencies) are built.Feature requests: what underlying problem are you trying to solve with this feature?
Fixing counter-intuitive command-line behaviour, reducing accidentally very long builds.
What operating system are you running Bazel on?
Ubuntu 18.04
What's the output of
bazel info release
?The text was updated successfully, but these errors were encountered: