Skip to content
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

Disable warnings-as-errors for release branches #33664

Merged
merged 2 commits into from
Mar 18, 2020
Merged

Disable warnings-as-errors for release branches #33664

merged 2 commits into from
Mar 18, 2020

Conversation

jkotas
Copy link
Member

@jkotas jkotas commented Mar 17, 2020

Fixes #33627

Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that warnings as errors will be disabled in master as well? I see the PR targets master and PRERELEASE is set to 1.

@jkotas
Copy link
Member Author

jkotas commented Mar 17, 2020

The warnings as errors are still going to be enabled in master.

This is a prep-work for when we flip PRERELEASE to 0 in release branches - it is what is going to disable warnings as errors.

@safern
Copy link
Member

safern commented Mar 18, 2020

Ah right, I miss read the condition.

@jkotas jkotas merged commit ef71836 into dotnet:master Mar 18, 2020
@jkotas jkotas deleted the PRERELEASE branch March 18, 2020 00:17
@@ -13,6 +13,10 @@ elseif(CLR_CMAKE_TARGET_ARCH_ARM64)
add_definitions(-DTARGET_ARM64)
add_definitions(-DTARGET_ARMARCH)
endif()
if (CMAKE_CXX_COMPILER_ID STREQUAL "GNU")
# The ABI for passing parameters with 32-byte alignment has changed in GCC 4.6
add_compile_options(-Wno-psabi)
Copy link
Member

@am11 am11 Mar 18, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jkotas, just wondering if warning as error state for PR runs is same as before (ON), why was this special case required for GCC as master was ok without it before this PR was merged?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR enabled warnings-as-errors for tests. The CoreCLR tests were built without -Werror before this change.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Disable warnings-as-errors in release branches
4 participants