-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Make Ignore Warnings suppress the output level entirely #4221
Conversation
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.
Thanks to previous build test failures, we can now truly "discard" the previous pr :)
Thanks @kaleb with a FANTASIC improvement for users! ❤️ |
Sorry for adding noise - I just wanted to say I'm really impressed with and appreciate the insane response time to #4213 |
74deb87
to
ef1589f
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Thanks for all your patience and guidance @yao-msft, It really helps me understand a lot more about why certain things have been done the way they are |
@Trenly I cannot merge due to merge conflicts. Can you merge to latest when you have time? Thanks. |
Should be good now |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Instead of handling each case individually, this PR makes the
--ignore-warnings
a common argument and suppresses all output fromcontext.Reporter.Warn()
. Support is added for enabling or disabling each reporter level individually.cc @yao-msft
Microsoft Reviewers: Open in CodeFlow