-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Silence Bazel warnings from external repositories #12358
Comments
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 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
Still a thing, though potentially a duplicate of #17030 |
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. |
This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please post |
Note that this is not the same as related questions about silencing warnings from external C++ dependencies, like #12009 (although I also spend quite a lot of time trying to get that working). I'm specifically talking about silencing Bazel warnings.
Description of the problem / feature request:
My project (https://github.com/google/iree) depends on some other projects that use Bazel. We have very little control over these dependencies. In particular, depending on TensorFlow comes with a boatload of warnings. Every time I have to build a target that loads tensorflow I get a nice preamble like:
Personally I'm of the opinion that warnings should almost always be errors or nothing (otherwise they just become log spam), but setting the more general philosophy aside, these are not warnings that we have much control over and I'd like to not see them every time I build.
Feature requests: what underlying problem are you trying to solve with this feature?
Add a flag to allow silencing WARNING messages from external repositories.
What operating system are you running Bazel on?
Linux Debian
What's the output of
bazel info release
?release 3.3.1 (but also reproducible with 3.7.0)
What's the output of
git remote get-url origin ; git rev-parse main ; git rev-parse HEAD
?Don't assume the default branch is
master
;-PHave you found anything relevant by searching the web?
No. https://google.com/search?q=bazel+warnings+from+external+repositories
The text was updated successfully, but these errors were encountered: