-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-2834] [Bug] Unable to convert deprecation warnings to errors #8130
Closed
2 tasks done
Tracked by
#7372
Labels
bug
Something isn't working
Comments
dbeatty10
added
bug
Something isn't working
triage
pre-regression
Regression not yet in a stable release
labels
Jul 18, 2023
github-actions
bot
changed the title
[Pre-regression] Unable to convert deprecation warnings to errors
[CT-2834] [Pre-regression] Unable to convert deprecation warnings to errors
Jul 18, 2023
4 tasks
dbeatty10
changed the title
[CT-2834] [Pre-regression] Unable to convert deprecation warnings to errors
[CT-2834] [Bug] Unable to convert deprecation warnings to errors
Jul 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a new bug in dbt-core?
Current Behavior
PASS
ing console output and a zero exit code instead of the expected behavior below.Expected Behavior
WARN_ERROR_OPTIONS
gives a mechanism whereby users can promote these warnings to actual runtime errors, and I expected a redFAIL
message in the console output and a non-zero exit code.Steps To Reproduce
models/my_model.sql
models/_models.yml
I was hoping for both of these to error out and have a non-zero exit code:
Relevant log output
No response
Environment
Which database adapter are you using with dbt?
postgres
Additional Context
No response
The text was updated successfully, but these errors were encountered: