-
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-846] Detailed timing
info not collected for models with error
status
#5476
Comments
timing
info not collected for models with error
statustiming
info not collected for models with error
status
Detailed timing information (including timestamps) would be available from the structured logging interface, which is where we're investing more of our effort around dbt Core metadata going forward |
Related: dbt-labs/dbt-snowflake#82 (comment) Even though the |
The
timing
array inrun_results.json
makes it possible to see the exact timestamps when a model started/finished compiling and executing. The array appears to be entirely empty if the resource encounters a runtime error.What users see in
run_results.json
, for anerror
model vs. asuccess
model:The relevant code is here, in the
compile_and_execute
method:dbt-core/core/dbt/task/base.py
Lines 336 to 340 in f988f76
The
collect_timing_info
context manager updates thetiming_info
attribute onself
. However, it never appendstiming_info
above ifself.run
encounters an error (e.g. a database error):The resolution to this bug would find a way to return/append/update the
timing_info
array even when the model encounters an error during its build.The text was updated successfully, but these errors were encountered: