-
Notifications
You must be signed in to change notification settings - Fork 408
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
Allow buildifier_test to escape the sandbox #1092
Conversation
084ef79
to
63313d6
Compare
We (opentitan-team) are curious if structuring global "whole project" tests like this is bad and if there is a better way for the test to find the root subdir of the project (tests don't have |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would love to see this merged as well :)
63313d6
to
136e25d
Compare
This allows buildifier_test to access the entire workspace to avoid needing to explicitly specify which files should be linted.
136e25d
to
edebdd1
Compare
Port of bazelbuild/buildtools#1092 (Don't love the ergonomics of these rules, but we've already invested in them I guess)
This allows buildifier_test to access the entire workspace to avoid needing to explicitly specify which files should be linted.
This PR addresses #1075 by adding a
no_sandbox
attribute and a WORKSPACE path attribute tobuildifier_test
. Currently, users must explicitly specify every BUILD file they would like to lint in thesrcs
attribute ofbuildifier_test
. This PR allows the user to create a test to lint all BUILD files as follows: