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
[tests] Enable TreatWarningsAsErrors=true #16766
Conversation
Sets `TreatWarningsAsErrors` to true when building template and sample projects to ensure that warnings are not missed.
/azp run |
Yay! ❤️ It would be good to deliberately cause a warning (e.g. change a template/sample to call some obsolete API, or some wacky version) and ensure it causes the type of failure we want to see, and that the failure correctly causes the PR checks to fail. (And then of course revert the warning before merging 😁 ) |
I added a warning case to one of the templates for testing, but am not sure why CI isn't triggering... |
Maybe CI is just bogged down and needed a minute to recover. Looks like it's woken up now. |
Azure Pipelines successfully started running 3 pipeline(s). |
Hum... not sure if this will block us of getting stuff merged .. but we will see. |
Yeah I think it's a worthwhile experiment. We'll see if it helps or hinders. But if it hinders a lot, then I think it points to a more serious problem of why we keep getting warnings showing up to begin with. |
Fixes: #16709 Sets `TreatWarningsAsErrors` to true when building template and sample projects to ensure that warnings are not missed.
Fixes #16709
Sets
TreatWarningsAsErrors
to true when building template and sampleprojects to ensure that warnings are not missed.