Skip to content

Commit 2e1a7fd

Browse files
committed
fix: skip dbt seed in integration_tests_2 fusion test
Fusion mis-resolves the path to the package's `dbt_project_evaluator_exceptions` seed when running `dbt seed` from a consuming project, producing a doubled `dbt_packages/dbt_project_evaluator/dbt_packages/dbt_project_evaluator/seeds/...` prefix and failing with an IO error. The seed isn't required here: integration_tests_2 only runs `dbt run` (not `dbt build`), so the on-run-end filter macro that reads the exceptions seed is never invoked.
1 parent 79160b9 commit 2e1a7fd

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

run_fusion_tests.sh

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,9 @@ dbt build -x --target $1 --full-refresh --static-analysis=off --vars "$FUSION_VA
1515
echo "Running Fusion tests for the second project"
1616
cd ../integration_tests_2
1717
dbt deps --target $1 || exit 1
18-
dbt seed --full-refresh --target $1 --static-analysis=off --vars "$FUSION_VARS" || exit 1
18+
# Skip `dbt seed` under Fusion: it mis-resolves the package seed path with a
19+
# doubled `dbt_packages/dbt_project_evaluator/...` prefix. Not needed here
20+
# because this project runs `dbt run` only (no tests → no exceptions lookup).
1921
dbt run -x --target $1 --full-refresh --static-analysis=off --vars "$FUSION_VARS" || exit 1
2022

2123
echo "Running Fusion tests for the SL project (new semantic layer spec)"

0 commit comments

Comments
 (0)