Remove duplicate logging during integration tests #4275
Merged
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 attemps to fix behavior that is unique to our integration testing framework. Adding (and re-adding) multiple log handlers, for multiple invocations-within-invocations, isn't something that should ever happen in real-world dbt use.
FILE_LOG
handlers before adding new oneSTDOUT_LOG
handlers before adding new one. The catch: only clearTextIOWrapper
handlers, to avoid messing upStringIO
stdout handler used byrun_dbt_and_capture
Before
After