Always pass error code to CI #9663
Merged
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
gaearon
commented
May 11, 2017
| console.log('Jest passed!'); | ||
| } | ||
| process.exit(0); | ||
| process.exit(code); |
Collaborator
Author
There was a problem hiding this comment.
This is the important part, others are just for consistency.
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.
During Rollup PR, we forgot to pass the error code from the Jest task.
As a result, master currently has a failing test.
The failing test was introduced in #9608.
This PR makes sure we always pass the code down.
It is expected to break CI.
In a followup PR we will look at the root cause.