-
Notifications
You must be signed in to change notification settings - Fork 989
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
Add core:warnings_as_errors
configuration option
#15149
Add core:warnings_as_errors
configuration option
#15149
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.
I was kind of expecting to raise an exception to produce a hard error, otherwise, it is just move error messages from yellow to read and WARN=>ERROR; but still can be skipped? And if we need to check for output, we can directly check the warnings.
conan/internal/deploy.py
Outdated
@@ -77,7 +77,7 @@ def _deploy_single(dep, conanfile, output_folder, folder_name): | |||
except Exception as e: | |||
if "WinError 1314" in str(e): | |||
ConanOutput().error("full_deploy: Symlinks in Windows require admin privileges " | |||
"or 'Developer mode = ON'") | |||
"or 'Developer mode = ON'", error_type="context") |
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.
What is a "context" error? The meaning is not evident to me
4bff9ee
to
974b568
Compare
Changelog: Feature: Add
core:warnings_as_errors
configuration option to make Conan raise on warnings and errors.Docs: conan-io/docs#3484
First try for
core:warnings_as_errors
. It worries me that people might want to have Conan stop processing on errors in this case (We mostly do that now when we print proper errors as they are next to raised exceptions), but I'm not quite sure if I should just raise here too. Any opinions are welcomed :)Closes #14909