https://linen.dev logo
Join Slack
Powered by
Hi All, We just upgraded to Elementary OSS 0.16.4...
# community-support
á
Hi All, We just upgraded to Elementary OSS 0.16.4 dbt and 0.16.2 python versions, coming from 0.15.2. I've noticed that the tests section on the report dashboard stopped showing singular tests which are defined under the 'tests' folder in our dbt project. We run the report 2 times a day, and you can see that the first report shows more dbt tests than the second. No tests have been added/removed between the two runs, the only difference is the elementary version used. Also, the charts at the bottom have all became empty, while previously they were filled correctly. Am I supposed to do anything special when upgrading Elementary versions? I've ran dbt run --select elementary. Thanks for your help
👍 1
m
Got the same issue upgrading this week - haven't found the issue/solution yet
n
Hey @Ádám Kocsis and @Marcelo Eichelberger 🙂 Tried reproducing this I do see my singular tests, but the dbt test count only included tests that weren't skipped on 
dbt build
. I see the singular tests that didn't run labeled as skipped. Do they not appear in your test result screen? What DWH are you using?
Screenshot 2025-02-25 at 12.52.15.png
á
Hi @Noya Offer! The test does appear in the Detection - Tests tab, and it has a status of Failed. Compared to your screenshot however, it is missing the Table name value. I'm using BigQuery
n
• Did you run a full refresh on Elementary tables at any point? • Can you try running 
dbt run
and 
dbt test
(instead of 
dbt build
)? Do this once and see if anything changes 🙂
á
I did not do a full refresh on the Elementary tables. After dbt run and dbt test it is still unchanged.
n
Got it. We'll take another look 💪
m
Hello @Noya Offer For me the same as for @Ádám Kocsis - except the the table name it is displayed, on "Detection - Tests" as well in "Performance - Test Performance". I've been running 
dbt-run
and 
dbt-test
and was getting the charts populated as expected until the upgrade. I'm using Snowflake. Thanks for your help!
n
@Marcelo Eichelberger So the issues your'e experiencing are less tests in the count and no historical data in the dashboard?
m
@Noya Offer - no, the test count is correct, its the historical data in the dashboard that is no longer being displayed
n
@Marcelo Eichelberger @Ádám Kocsis Do you have data on 
elementary_test_results
from dates previous to the version update?
And also, since the update did the data on the dashboard populate or is it still empty?
á
Hi @Noya Offer, Yes, the 
elementary_test_results
table has data from before the version update too. The charts at the bottom of the dashboard are still empty, and the singular tests are still not counted towards the 'dbt tests' total.
🙏 1
n
Got it. Seems like a bug in the new CLI version, our engineers are looking into it! Thank you for bringing this up, I'll keep you updated 😊
á
Thank you for the support!
🙌 1
n
Hey @Ádám Kocsis @Marcelo Eichelberger, We will release a new CLI version tomorrow with the fixed graphs. Thank you for bringing this to our awareness! drop corrupt happy🙌
keanu thanks 1
@Ádám Kocsis Is the test issue still happening?
á
@Noya Offer Yes, the same problems still persist, but thank you, I will test it again after the new version comes out.
🙏 1
Hi @Noya Offer, I've re-run the report using the new 0.17.0 dbt and python version, and the graph indeed shows some signs of life, but strangely only 1 day is filled of the last 7. Maybe it will show proper values when the next dbt run and dbt test commands are executed. Regarding the missing tests: I do not see a change, it still misses the singular tests from the 'dbt tests' section of the dashboard.
Should i run 'dbt run --select elementary' again?
n
Hey @Ádám Kocsis, the graphs should keep updating with the next runs over the next few days. There's no need to rerun the Elementary tables 🙂 As for the singular tests, do the tables they test run properly? What do you see in your 
dbt test
logs?
a
Hi @Noya Offer we are facing the same issue with singular tests and dashboard graphs. We are using 
elementary-data[bigquery]==0.17.0
and dbt package 
elementary-data/elementary 0.17.0
.
logs gives the following information about tests
Copy code
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15  Completed with 4 warnings:
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15  Warning in test assert_raw_language_has_ref_code_iso_639_set_1 (tests/singular/models/marts/dm/member/assert_raw_language_has_ref_code_iso_639_set_1.sql)
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15  Got 2 results, configured to warn if != 0
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15    compiled code at target/compiled/emr_data_transformation/tests/singular/models/marts/dm/member/assert_raw_language_has_ref_code_iso_639_set_1.sql
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15    See test failures:
  ------------------------------------------------------------------------------------------------------------------
  select * from `sxp-emr-integration-staging`.`emr_dbt_test__audit`.`assert_raw_language_has_ref_code_iso_639_set_1`
  ------------------------------------------------------------------------------------------------------------------
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15  Warning in test assert_raw_ethnicity_has_ref_code (tests/singular/models/marts/dm/member/assert_raw_ethnicity_has_ref_code.sql)
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15  Got 6 results, configured to warn if != 0
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15    compiled code at target/compiled/emr_data_transformation/tests/singular/models/marts/dm/member/assert_raw_ethnicity_has_ref_code.sql
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15    See test failures:
  -----------------------------------------------------------------------------------------------------
  select * from `sxp-emr-integration-staging`.`emr_dbt_test__audit`.`assert_raw_ethnicity_has_ref_code`
  -----------------------------------------------------------------------------------------------------
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15  Warning in test assert_raw_language_has_ref_code_iso_639_set_2 (tests/singular/models/marts/dm/member/assert_raw_language_has_ref_code_iso_639_set_2.sql)
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15  Got 2 results, configured to warn if != 0
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15    compiled code at target/compiled/emr_data_transformation/tests/singular/models/marts/dm/member/assert_raw_language_has_ref_code_iso_639_set_2.sql
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15    See test failures:
  ------------------------------------------------------------------------------------------------------------------
  select * from `sxp-emr-integration-staging`.`emr_dbt_test__audit`.`assert_raw_language_has_ref_code_iso_639_set_2`
  ------------------------------------------------------------------------------------------------------------------
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15  Warning in test assert_raw_race_has_ref_code (tests/singular/models/marts/dm/member/assert_raw_race_has_ref_code.sql)
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15  Got 1 result, configured to warn if != 0
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15    compiled code at target/compiled/emr_data_transformation/tests/singular/models/marts/dm/member/assert_raw_race_has_ref_code.sql
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15    See test failures:
  ------------------------------------------------------------------------------------------------
  select * from `sxp-emr-integration-staging`.`emr_dbt_test__audit`.`assert_raw_race_has_ref_code`
  ------------------------------------------------------------------------------------------------
[2025-03-17, 13:43:15 UTC] {logging_mixin.py:190} INFO - 13:43:15
we can't see this test warnings on the main dashboard but we see this tests on the tests tab
n
Hey @Anton Ketska, our FE team is looking into it. Will update soon!
thankyou 1
a
@Dmitrii Drik FYI
@Noya Offer Hi any news on this problem?
n
Hey, did some digging with our product team. This is not a bug - we don't yet support singular tests as well as we support other tests, as Elementary requires a clear connection between a test and a table. Creating better support on both OSS and the Cloud is definitely on our Product roadmap! For now, if you're using 
{{ ref (model) }}
or this solution within your test .sql file, the table and the test will be connected and presented in the UI. Let me check if we can start with surfacing the warnings to the main dashboard so the information isn't missing.
a
Thanks. We will try to add 
override_primary_test_model_id
to our singular tests and will inform you if it helps
🙌 1
Hi, @Noya Offer. Adding 
override_primary_test_model_id
to singular tests solved the problem and dashboard graphs is visible after switching browser language to English (United States). Thank you for your support
40 Views
Open in Slack
PreviousNext
Powered by