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
{{ message }}
This repository has been archived by the owner on Dec 15, 2023. It is now read-only.
@moshir I was going to recommend running pytest -s test/integration/myadapter.dbtspec, which will prevent pytest from "capturing" debug-level logs and instead print them to stdout. It looks like you've managed to do that with --log-level DEBUG. So you're already in decent shape!
Could you provide a bit more context for the log snippet you've included? Are those steps 6-8 of test_dbt_empty? Does it seem that step 8/8 is where failure takes place?
If so, step 8 in the empty sequence is a catalog comparison step:
Basically, dbt wants to introspect the database to double-check that all the sources it expects to be there, and all the nodes it expects to have just created, are indeed present. (Of course, In the case of the empty project, there are 0 sources and 0 models.) It does that by inspecting the catalog.json artifact produced by the previous docs generate step. Here's the code snippet that defines catalog comparison:
when running
pytest --log-level DEBUG test/integration/myadapter.dbtspec
i see the test has failed
(i've tried to change pytest options, with no success)
Any pointer about how to debug this ?
The text was updated successfully, but these errors were encountered: