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
A test's lifecycle looks something along the lines of:
create a temp dir
cd to this temp dir
symlink everything in the test module directory of the current test being run to this temp dir (ex: everything in test/integration/068_partial_parsing_tests)
write dbt_project.yml , profile, and other project files to this temp dir
This solution copies and deletes files in a directory in the temp dir that is not symlinked back to the source code. This is still not ideal, I want to use this opportunity to try out a better approach to protect from ending up in this scenario in the future.
Is there an existing issue for this?
Current Behavior
Tests that move files in order to recreate user behavior modify python source code which can lead to failures when running tests in parallel.
Example of workflow failing: https://github.com/dbt-labs/dbt-core/runs/3887780692?check_suite_focus=true#step:9:1350
Example of test that moves files:
dbt-core/test/integration/068_partial_parsing_tests/test_partial_parsing.py
Lines 26 to 215 in fd7c95d
Expected Behavior
Tests should be able to run in parallel.
Steps To Reproduce
I've been able to reproduce by running test in parallel locally. Something like:
python -m pytest -n12 -m profile_postgres test/integration
Relevant log output
No response
Environment
No response
What database are you using dbt with?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: