ci: add importer to direct jest non-error output to stdout #4375
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.
Description
jest
has an issue where non-error reporting also goes to stderr (see this issue jestjs/jest#5064). This seems to be a long-running issue and one of the solution that's emerged is to use thejest-standard-reporter
package as a reporter in jest config to properly direct output.Our trigger for this is to be able to see test reporting as tests are executed in buck instead of having to wait to the end of the test run when stderr is collected and dumped to the terminal.
This segregation has additional potential benefits if we ever end up using any ci tooling that depends on error messages going to stderr and regular output going to stdout.