-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
"MongoMemoryReplSet" in "jest" gives open handle error #213
Comments
@j does this still happen on later versions of this package? and could you provide your used mongodb version? |
MongoMemoryReplSet
in jest
gives open handle error
i think #166 is related |
Which later version, I am facing this in package version 6.9.2, |
An Process didnt exit with signal "SIGINT" within 10 seconds, using "SIGKILL"!
|
@abishek28007 your "warning" has nothing to do with this issue, it comes when |
@hasezoey I posted the underlining log
|
@abishek28007 this seems like you didnt await an |
yup using |
works fine for |
@abishek28007 this case is known and already fixed in 7.0.0 (beta), will not be fixed in an 6.x release (because it requires refactor of some code) |
@hasezoey which beta version I updated to |
@abishek28007 every beta below 7 is an broken build (build process was not called directly), so use that at lowest if using beta - this warning (for replsets) got fixed in 6 (but like i said, broken build) -> because the beta is still ongoing, there are no deprecation warnings yet on an 6.x release |
@hasezoey not sure what was added in beta 7 but getting |
@hasezoey error for
|
@abishek28007 like i said, there isnt an "smooth" transition release yet, please read the changelog on what changed
this is because aside from this, |
Hello, Thanks! P.S.: I'm also experiencing this in Mocha, not just Jest. |
@jverce no, basically the "smooth shutdown" is just not released yet, so either wait for it to use SIGKILL, or try to use 7.0 beta |
I am experiencing the same issue. Tried to update to ^7.0.0-beta.1, and changed to:
But the database never comes online. An exception is catched inside the tmp module saying that @hasezoey do you have any suggestions? I have a lot of testcases and running all of them takes quite a while, when I need to wait the 10 sec for the SIGKILL :-) |
@JonasWestAlro please open an new issue, with all the information required PS: all 7.0.0 betas below .7 were broken, and if possible always use the latest beta |
If I close the client &
await replSet.stop()
, jest spits out an error:If I don't use a replset, then it works.
If I replace the above with just a single mongo server and stop it, it works.
The text was updated successfully, but these errors were encountered: