-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jest tests hanging forever with large snapshot changes #5392
Comments
/cc @pedrottimark could you take a look at this? My guess is that the diff generation ends up in some sort of loop, preventing both the diff from being generated, and the test from timing out. |
@SimenB @digitalsadhu Yes, this looks like same problem #1772 which I have been working on. Very timely to have more offline stress tests. I will put received and expected serializations into separate files to measure heap used by improved |
@digitalsadhu Unrelated to the problem, is there a duplicated assertion in |
And the winner is
Unlike previous example from React, this example has similar number of expected and received lines and a smaller (almost a quarter though) proportion of changed lines:
|
Thanks for digging in! Are you saying this is a duplicate of #1772, and can be tracked there? Is there anything we can do currently to at least be able to time out the test? Or should we just wait until the underlying issue is fixed? |
@pedrottimark hah! right you are. Very punny. ;) |
@SimenB We can let this shorter issue be primary and the earlier longer issue be secondary.
|
Hi @pedrottimark , We are also facing the same issue. Are there any updates? Did you get a chance to open a pull request? |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Jest tests hanging forever when there have been large snapshot changes. Running
jest -u
seems to fix the issue.Reproduce by pulling down this branch and running
jest
. It should sit spinning forever. Runjest -u
to fix. Subsequent calls tojest
should work.The text was updated successfully, but these errors were encountered: