Suppress Build Summary Message for JSON Output Mode #702
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
externl
approved these changes
Sep 10, 2024
InsertCreativityHere
changed the title
pepone
approved these changes
Sep 10, 2024
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.
This PR fixes: icerpc/icerpc-csharp#4043.
Now, we don't emit the summary message unless
slicecis using theHumanDiagnosticFormat(the default).Since otherwise, we expect a tool to be consuming the output, and it doesn't care about this summary.
I ripgrepped, and the only two places where we write to stdout or stderr were when we emit the diagnostics (which was already properly JSONified) and the summary message.