Log to stdout on non-Windows platforms #1763
Closed
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
We need to print to stdout on Windows because printing to stderr causes XCTest execution to deadlock when running tests in parallel on Windows. But printing to stdout causes XCTest to interleave process output with its own output, which creates hard-to-read log. To avoid this, print to stderr on all other platforms.
|
@swift-ci Please test |
bnbarham
approved these changes
Oct 16, 2024
|
Closing in favor of #1765 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
We need to print to stdout on Windows because printing to stderr causes XCTest execution to deadlock when running tests in parallel on Windows.
But printing to stdout causes XCTest to interleave process output with its own output, which creates hard-to-read log. To avoid this, print to stderr on all other platforms.