You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
PASSing 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 red FAIL message in the console output and a non-zero exit code.
github-actionsbot
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
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
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: