Document slow tests on certain CI servers and/or Docker machines. #2162
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
Current coverage is 88.57% (diff: 100%)@@ master #2162 diff @@
==========================================
Files 39 39
Lines 1409 1409
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
Hits 1248 1248
Misses 161 161
Partials 0 0
|
This was referenced Nov 29, 2016
|
thank you! |
tushardhole
pushed a commit
to tushardhole/jest
that referenced
this pull request
Aug 21, 2017
…stjs#2162) * Document slow tests. * Add "up to".
|
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. |
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.
Hey guys, me and a bunch of others users have found that Jest may be slow on CI servers and/or Docker machines. This is probably related to limited IOPS or CPU power. Until there's a solution I recommend documenting it in the troubleshooting guide. Suggestions for improvement are welcome.