Open moshir opened 3 years ago
@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:
Hope this helps a bit with your debugging.
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 ?