Modified large_trigger_record_test.py to correctly compare the names … #470
Conversation
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
added 2 commits
December 30, 2025 12:52
…of the configurations with the current test name when determining which datafile validation values to use.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…of the configurations with the current test name when determining which datafile validation values to use.
Description
The recent addition of the process manager type to the name of the current test in our integtests broke an "if" clause in the
large_trigger_record_test. This changes fixes that oversight.The problem was identified when the
large_trigger_record_testwas run, and running it with the fix should now work without any problems.Type of change
Testing checklist
dbt-build --unittest)dfmodules_integtest_bundle.sh)Further checks