Chore: Fix flaky test by unliking dbt msgpack for deterministic behaviour#5479
Merged
themisvaltinos merged 1 commit intomainfrom Oct 3, 2025
Merged
Chore: Fix flaky test by unliking dbt msgpack for deterministic behaviour#5479themisvaltinos merged 1 commit intomainfrom
themisvaltinos merged 1 commit intomainfrom
Conversation
georgesittas
approved these changes
Oct 3, 2025
Collaborator
|
Oh man, nice work figuring this one out! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This aims to fix the flaky test
test_run_with_changes_and_full_refresh. This fails intermittently because when the test modifies model_b.sql, dbt's change detection mechanism doesn't always register the update due to the limited granularity of filesystem timestamps. So dbt may rely on a stale cached model definition, which doesn't include the updated schema with the new column c. The fix is to explicitly unlink the partial parse cache file after modifying the model, which forces dbt to perform a full parse and register the changes.