Hi there. I'm having a hard time visualizing the r...
# community-support
n
Hi there. I'm having a hard time visualizing the results of my tests with
edr report
. I have a profiles.yml like:
Copy code
dbtpoc:
  outputs:
    dev:
      dbname: pipelinedb
      host: localhost
      pass: ...
      port: ...
      schema: dbt_tests
      threads: 4
      type: postgres
      user: ...
  target: dev

elementary:
  outputs:
    default:
      type: postgres
      host: localhost
      user: ...
      password: ...
      port: ...
      dbname: pipelinedb
      schema: dbt_tests_elementary
      threads: 4
The only configurations in my dbt_project.yml are:
Copy code
models:
  elementary:
    +schema: elementary

flags:
  require_explicit_package_overrides_for_builtin_materializations: false
  source_freshness_run_project_hooks: True
Then, if I do
dbt run
followed by
edr report
, I see a nice report with my models built. However, if I follow that up with
dbt test
and run
edr report
again, I get a "No test results" report, also without my models. If I click on "Model performance" on the right menu, I also see an infinite spinning wheel as it tries to fetch models, but nothing is shown. I have checked that 1.
pipelinedb.dbt_tests_elementary.elementary_test_results
has content 2. There are no errors in
edr_target/edr.log
3. The command
dbt run-operation elementary.log_macro_results --args '{"macro_name": "elementary_cli.get_tests"}' --project-dir [folder in the logs]
returns valid content Would anyone have suggestions for where to look for the reason the report is not able to show test results?
This is the edr.log file
And this is the spinning wheel I mentioned
edr_target/elementary_output.json also looks good, as far as I can tell
Hi @Elementary Support, I was wondering if anyone could share thoughts here. I tried chatting with the AI bot, but I couldn't fix the issue yet.
n
Hey @Naza! It seems like you're running
--last_invocation
, can you try running
edr report
by itself?
n
Hi @Noya Offer. I am calling just 'edr report' on the terminal. Is there a way I can force it to not use the --last_invocation flag? Also, I've narrowed down the issue to a specific test (or occasionally tests) that breaks reporting.