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
for the test_executions data, the two fields "compile_started_at" and "query_completed_at" are always null.
How to reproduce
Run anything and check the test_executions.
Expected behaviour
Both fields should be properly extracted from the run results.
Screenshots
Environment
Results of running dbt --version:
dbt core 1.7.11, dbt artifacts 2.6.2 on databricks
Potential Fix
Seems like there was a copy/paste error. Changing the model.timing to test.timing (for compile started at and query completed at) fixes this. Seems like this was overlooked.
The text was updated successfully, but these errors were encountered:
Overview
for the test_executions data, the two fields "compile_started_at" and "query_completed_at" are always null.
How to reproduce
Run anything and check the test_executions.
Expected behaviour
Both fields should be properly extracted from the run results.
Screenshots
Environment
Results of running
dbt --version
:dbt core 1.7.11, dbt artifacts 2.6.2 on databricks
Potential Fix
Seems like there was a copy/paste error. Changing the model.timing to test.timing (for compile started at and query completed at) fixes this. Seems like this was overlooked.
The text was updated successfully, but these errors were encountered: