-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Enable warnAsError for correctness builds #39014
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
Conversation
|
Build logs showing a failing correctness build due to formatting errors. Other legs successfully built and started running tests. |
|
Overall looks good. Think we need to also make the following changes: When building the desktop legs we should not pass warnAsError and should pass skipAnalyzers. That way the desktop leg is focused on running teests while the correctness leg is focused on build correctness including analyzers, formatting, etc .... https://github.com/dotnet/roslyn/blob/master/azure-pipelines.yml#L40 We should be able to enable MSBuild's warn as error without qualification now here https://github.com/dotnet/roslyn/blob/master/eng/build.ps1#L231 |
|
Build logs showing failing correctness leg |
|
@jaredpar Did I get those changes right? |
jaredpar
left a comment
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 have been instructed by the author to hit the button |
These changes setup the Correctness Test leg to fail when the formatting analyzer reports warnings. Other test legs will ignore these warnings and run unit tests as expected. Local builds (
.\build.cmdand VS) will report warnings but not fail the build.