-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Enable /warnAsError
#23072
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
Enable /warnAsError
#23072
Conversation
dougbu
commented
Jun 18, 2020
- Allow some warnings related to closed issues
/fyi will run an internal pipeline once we drive warnings down enough for PR validation to succeed. We have a small amount of site extensions code that doesn't build in PR validation. |
As expected, #22992 blocks this. Warnings mentioned there are visible in all test builds. |
|
||
# Disable node reuse - Workaround perpetual issues in node reuse and custom task assemblies | ||
$nodeReuse = $false | ||
$env:MSBUILDDISABLENODEREUSE=1 | ||
|
||
# Our build often has warnings that we can't fix, like "MSB3026: Could not copy" due to race | ||
# conditions in building C++ | ||
# Fixing this is tracked by https://github.com/dotnet/aspnetcore-internal/issues/601 |
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.
Reminder to self: Close dotnet/aspnetcore-internal#601 when this PR goes in 😺
- already enabled in non-Windows builds because override existed only in build.ps1
- common `<NoWarn>$(NoWarn);CS1591</NoWarn>` case unchanged - /Directory.Build.props ensures that warning remains a warning but doesn't hide it
- variable eng/common/tools.sh uses named `warn_as_error`
7abb247
to
2738e1e
Compare
Internal build https://dev.azure.com/dnceng/internal/_build/results?buildId=694625 built all product code, including site extensions. That build did not compile any test code but PR validation build https://dev.azure.com/dnceng/public/_build/results?buildId=694621 covered that. Both hit only the expected (for now) 8 or 9 per-build non- |