Skip to content
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

report issue: Missing Test Execution TIme in Test Execution History tab #1675

Closed
KraevRoot opened this issue Aug 19, 2024 · 3 comments
Closed
Labels
Bug Something isn't working Triage 👀

Comments

@KraevRoot
Copy link

KraevRoot commented Aug 19, 2024

Describe the bug
Execution time in Test Execution History tab is not populated for all tests.

To Reproduce
Steps to reproduce the behavior:

  1. dbt seed --select XXX
  2. dbt run --select XXX
  3. dbt test --select XXX
  4. edr send-report -slack-token XXX --slack-channel-name XXX --config-dir XXX --env dev --profiles-dir XXX --target-path XXX --days-back 14

Expected behavior
Execution time in Test Execution History tab is visible and has correct values.

Screenshots
Screenshot from 2024-08-19 12-28-23

Environment (please complete the following information):

  • Elementary CLI (edr) version: [0.15.1]
  • Elementary dbt package version: [0.15.2]
  • dbt version you're using [1.8.2]
  • Data warehouse [snowflake]

Additional context
This query returns the correct execution time for each test ( matches cli output ):

select * from XXX.ELEMENTARY.DBT_RUN_RESULTS where resource_type = 'test' order by generated_at desc limit 200;

So it looks like the issue is that the edr for some reason can't get the tests' execution time from the database.

Would you be willing to contribute a fix for this issue?
Yes

@KraevRoot KraevRoot added Bug Something isn't working Triage 👀 labels Aug 19, 2024
@KraevRoot
Copy link
Author

Hmm, the current_tests_run_results_query.sql query returns a bunch of results where all execution_time values are null

@KraevRoot
Copy link
Author

KraevRoot commented Aug 19, 2024

this query returns 48k results

select count(*) from XXX.ELEMENTARY.dbt_run_results;

but,

select count(*) from XXX.ELEMENTARY.dbt_run_results where execute_completed_at is not null

returns zero results

So the issue is that filtering the dbt_run_results table by execute_completed_at column produces 0 results, because this field is not populated for some reason

@KraevRoot
Copy link
Author

Fixed in 0.16.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Triage 👀
Projects
None yet
Development

No branches or pull requests

1 participant