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
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
@mikealfare asked me to file this bug. I've seen a small number of functional tests leaving behind schemas/tables, typically because they create a schema that is not enumerated in the manifest. In particular, I have seen the following tests do this without significant modification for my adapter:
BaseSameAliasDifferentSchemas
BaseSameAliasDifferentDatabases
I have also seen the following tests have this issue, but I'm much less confident it wasn't related to a change that I had to make for Databricks:
dbt_debug - test_ok
dbt_clone - test_clone_same_target_and_state
Note: I'm hitting this in 1.7.x, so nothing specific to the adapter decoupling effort, but was asked to file here.
Expected Behavior
All tests clean up all schemas when they're done
Steps To Reproduce
Run the specified tests.
Relevant log output
No response
Environment
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Is this a new bug?
Current Behavior
@mikealfare asked me to file this bug. I've seen a small number of functional tests leaving behind schemas/tables, typically because they create a schema that is not enumerated in the manifest. In particular, I have seen the following tests do this without significant modification for my adapter:
I have also seen the following tests have this issue, but I'm much less confident it wasn't related to a change that I had to make for Databricks:
Note: I'm hitting this in 1.7.x, so nothing specific to the adapter decoupling effort, but was asked to file here.
Expected Behavior
All tests clean up all schemas when they're done
Steps To Reproduce
Run the specified tests.
Relevant log output
No response
Environment
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: