[rush] Fix logging for non-zero exit codes #4984
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.
Summary
Fixes #4882
Child process that only writes to stdout but is configured to exit with code 2.


Before:
After:
Details
With this change, Rush internally writes any fatal error from an Operation to the
stderr
stream of theStdioSummarizer
instead of thestdout
stream. This effectively makes the error seen by Rush be treated as lower priority for the logs than anystderr
output from the Operation itself.How it was tested
Added
process.exitCode = 2
to the end of the build script in api-extractor-lib1-test.Impacted documentation
Anything about the error reporting for non-zero exit codes.