-
-
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 can hang indefinitely in node 12 #9729
Comments
Any news on this? We're seeing something similar with node 12.16.1 and deasync |
@bluesxman I added a repo that can reproduce this issue on demand but it got tagged as needs repro so I am not sure how the process works. What js library are you using that uses |
We get infinitely hanging tests in Shepherd when we try to bump from node 10 to 12. Not sure if that is helpful? |
For what it's worth our solution was to stop using deasync since its potentially problematic. I made an async alternative to what we were using deasync for. |
I don't think we're using |
Turns out we were using deasync from jest-transform-svelte. Moving away from it fixed things for us. |
Same issue encountered, is there any workaround besides remove |
Not that I know of. |
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
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. |
🐛 Bug Report
Jest can hang indefinitely in node 12. I have seen this issue in docker and on osx.
To Reproduce
Steps to reproduce the behavior:
Call a library like
get-port-sync
during a jest run on node 12. I think deasync could be triggering this but I am not sure.Expected behavior
Link to repl or repo (highly encouraged)
https://github.com/pllee/jest-get-port-sync
The text was updated successfully, but these errors were encountered: