fix missing console.log messages#3895
Merged
boujeepossum merged 2 commits intojestjs:masterfrom Jun 23, 2017
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3895 +/- ##
==========================================
- Coverage 58.07% 58.01% -0.07%
==========================================
Files 195 195
Lines 6734 6741 +7
Branches 6 6
==========================================
Hits 3911 3911
- Misses 2820 2827 +7
Partials 3 3
Continue to review full report at Codecov.
|
Contributor
|
@aaronabramov oh, cool! |
tushardhole
pushed a commit
to tushardhole/jest
that referenced
this pull request
Aug 21, 2017
* Ensure that console output is not lost in concurrent reporter * console.log integration test + naming
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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
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.
this is a split from #3882
fixes #3755
thanks @valerybugakov for finding this.
Console mesasges weren't being printed because we debounce the output for concurrent reporter, and some of the messages didn't have enough time to print before the process exits