This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
[ios, osx] The return of xcpretty, part II #4676
Merged
Conversation
This file contains 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
|
@1ec5 @friedbunny Thoughts? |
|
👍 Raw xcodebuild output is sometimes useful, but it has also been obscuring some warnings like the one I finally noticed while working on #4641 and fixed in 1b09898e03aad3029bb276bc3fd429a102348c35. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Bring back xcpretty. We've encountered issues with it in the past, but I'm willing to go back to it because the alternative -- immensely verbose build logs in which it is virtually impossible to find error output -- is worse.