Update Jest test runner to version 20.0.4 #2251
Merged
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
gregaubert
force-pushed
the
feature/greg/update_jest_test_runner
branch
from
d0f84b7
to
843ffbe
Compare
gregaubert
force-pushed
the
feature/greg/update_jest_test_runner
branch
from
843ffbe
to
43b676f
Compare
gregaubert
force-pushed
the
feature/greg/update_jest_test_runner
branch
from
43b676f
to
35e6b71
Compare
gregaubert
force-pushed
the
feature/greg/update_jest_test_runner
branch
from
35e6b71
to
f2d095c
Compare
|
@stas-vilchik We probably need to also merge this, since the other PR is using a |
stas-vilchik
approved these changes
Aug 15, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Trying to update the version of Jest to prevent a memory leak that is affecting our tests : jestjs/jest#1893
Running the tests with Jest version 19.x would use up to 1.6Gb Ram, making the tests fail on Travis.
Unfortunately updating to version 20.0.4 does not bring a big improvement, we only went down to 1.4Gb consumption, so the leak is still there.
Jest is using babel-polyfill automatically if the module is available, so trying to remove the dependency to babel-polyfill shows a little better results, down to max 900Mb Ram used.
But that would mean we need to drop babel-polyfill and it's still used for older browsers.