-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
dbt run
summary reports incorrect SKIP= numbers
#2095
Comments
Here we go. The |
Thanks for the report @brangisom - I'm prioritizing this one for our 0.16.0 Barbara Gittings release. Is this something you'd be interested in contributing a fix for? I took a quick look here, and it the issue appears to be that we set the value I think the fix is to add a Set via |
Yeah, I think I can knock that out this week. |
Describe the bug
A clear and concise description of what the bug is. What command did you run? What happened?
When I do
dbt run --models some_model+
, if some_model fails, and it's dependencies SKIP, the final summary reportsDone. PASS=4 WARN=0 ERROR=1 SKIP=0 TOTAL=5
Steps To Reproduce
In as much detail as possible, please provide steps to reproduce the issue. Sample data that triggers the issue, example model code, etc is all very helpful here.
dbt run --models any_model+
with dependencies, ensuring thatany_model
fails. The dependent models will SKIP, but the output will not record the number of skipped models.Expected behavior
A clear and concise description of what you expected to happen.
dbt run --models any_model+
should report the correct number of skipped models in the final summary.Screenshots and log output
If applicable, add screenshots or log output to help explain your problem.
System information
Which database are you using dbt with?
The output of
dbt --version
:The operating system you're using:
Whatever I get out of
docker build
viaFROM python:3.7.4
. If it becomes important I can figure it out.The output of
python --version
:Python 3.7.4
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: