Skip to content

test: make seed parsing rerun-safe - #1757

Open
sd-db wants to merge 4 commits into
databricks:mainfrom
sd-db:sd-db/fix/seed-parsing-rerun
Open

sd-db wants to merge 4 commits into
databricks:mainfrom
sd-db:sd-db/fix/seed-parsing-rerun

Conversation

@sd-db

@sd-db sd-db commented Oct 28, 2026

Copy link
Copy Markdown
Collaborator

Description

An interrupted TestSeedParsing setup can leave seed_expected behind, causing automatic retries to fail with TABLE_OR_VIEW_ALREADY_EXISTS. Drop that setup table before recreating it, and use the existing rerun-safe fixture to reset the model and seed relations between attempts.

This is a test-only repair. The inherited parsing checks remain unchanged. The initial failure that triggered the reported CI retries is still unknown.

Validation

  • Reproduced the leftover-table error on the unmodified base with an injected setup interruption.
  • Ran the repaired seed test normally on a Unity Catalog SQL warehouse: 1 passed.
  • Injected a setup interruption: 1 passed, 1 rerun in the same schema.
  • Injected a failure after the complete test body: 1 passed, 1 rerun; both test executions completed in the same schema.
  • All five pre-commit hooks passed.

Checklist

  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.
  • [Optional] I have run the dbt-databricks-pr-ready project skill for this PR and addressed its merge-readiness feedback

@github-actions

Copy link
Copy Markdown

Coverage report

This PR does not seem to contain any modification to coverable code.

Co-authored-by: Isaac <no-reply@databricks.com>
@sd-db sd-db changed the title Make the seed parsing test rerun-safe test: make seed parsing rerun-safe Oct 29, 2026
@sd-db
sd-db marked this pull request as ready for review October 30, 2026 09:07

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants