-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
SIGNREQUEST when using DockerComposeEnvironment #346
Comments
Unfortunately not, I'm still seeing this occasionally unless I add manual timeouts! |
@TheTFo could you pls share the version of Jest you are using? |
Just seeing this, I'll get you this in the morning! Thanks for the help!
…On Mon, Apr 11, 2022, 4:54 AM Cristian Greco ***@***.***> wrote:
@TheTFo <https://github.com/TheTFo> could you pls share the version of
Jest you are using?
—
Reply to this email directly, view it on GitHub
<#346 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEBNIFYMXXKFBMQRGD4OFLVEPSDZANCNFSM5S47FD3Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I'm using Jest 27.5.1 with ts-jest 27.1.4. Hope that helps! I should add, I've removed the CLI args indicating open handles for now and things seem to be running fine. I generally like to run with it with TestContainers as it's pretty easy to leave them open. |
Try something like this: const l = await redisContainer.logs()
l.destroy()
await sleep(500) |
FYI I've raised an issue with |
The PR for jest has been merged (jestjs/jest#12789). Waiting for the next release to confirm and close this issue. |
Should be fixed in Jest v28.1.0, could anyone please confirm? |
@cristianrgreco Can confirm, I can't reproduce the issue using my steps from #310 ! Thanks a lot for looking into and fixing this! |
Great! And thank you @SkySails for bringing this issue to my attention and for your help in resolving it! 🙂 |
Thanks Cristian
…On Fri, Apr 29, 2022, 8:47 AM Cristian Greco ***@***.***> wrote:
FYI I've raised an issue with ssh2, will be tracking that for more
information/progress.
—
Reply to this email directly, view it on GitHub
<#346 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEBNIGAK2S7EDN2FQFVAQLVHPK6LANCNFSM5S47FD3Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Expected Behaviour
Jest + Test Containers exits cleanly
Actual Behaviour
Receiving error "SIGNREQUEST"
Testcontainer Logs
Steps to Reproduce
Note: Using docker-compose for this, and not the pre-built kafka container, because I also want schema registry
Using docker-compose
With this test file
Started with:
NODE_ENV=development jest --config=e2e/jest.config.js --runInBand --bail --verbose --logHeapUsage --detectOpenHandles --forceExit
Environment Information
The text was updated successfully, but these errors were encountered: