Fix capture output when running tests that call the ConanRunner in the conanfile #7799
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.
Changelog: Fix: Fix capture output when running tests that call the ConanRunner in the conanfile.
Docs: omit
When the ConanRunner was called inside the conanfile the output was not correctly captured depending the case, making imposible to make tests that check the self.run method output. This was because _UnbufferedWrite was encapsulating the ConanOutput and checking if the output had to be captured was returning the wrong results:
conan/conans/client/runner.py
Lines 79 to 85 in 558a2ce