-
-
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
[Bug]: Tests appear to stall quietly with V28 #12972
Comments
@phawxby why was this closed? Did you find a solution? 🙏 We observe the same issue of silently hanging tests on a fairly large test suite. |
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. |
Version
28.1.1
Steps to reproduce
I'm not really sure how to demonstrate a repro case for this, it's a private repository and i'm fairly confident at this point it's due to the size of our repository. I'm hoping this provides a place for others to also notify if they're experiencing the same.
My gut feeling at this point is it's to do with us approaching the memory limit on the machine, which is obviously a problem, but it should probably output some kind of more helpful message than just stalling out and not doing anything until it times out. I'm assuming this based on the tests completing without coverage so memory limits aren't a problem.
Node 16.10.0 use because of this issue.
Jest 27.4.1 with coverage
Jest 28.1.1 with coverage.
Test step timed out at 9m 18s. Time in the job up until the start of the test step was about 1m. So roughly 5m from the start of the job until it stopped outputting.
Jest 28.1.1 without coverage.
(Ignoring the test failure, it's a known flakey test we need to fix)
Expected behavior
Some kind of error message regarding lack of memory or something.
Actual behavior
Tests appear to stall with no output.
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: