Jest did not exit one second after the test run has completed.

[EtienneDx]

Hi, I've been wrapping my head around this for a few days now, but it seems that jest refuses to exit after the tests are finished. I checked the debug, the teardown is properly executed, but I have the following message popping up every time whatever I try:

Jest did not exit one second after the test run has completed.

This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.

I've been running the test on windows 10, both on a directory with real test and on a directory with a single expect(true).toBe(true) and nothing seems to work. Any idea of what I could do?

[jbeale]

Make sure you don't have anything in your local environment (some cough certain internal company cough build systems do this) that encapsulates new Node child processes in another environment script before actually launching them. If your build system does that by wrapping node, then Node will receive the PID of the wrapper script instead of the actual DDBLocal Java process. When the dynamodb-local script goes to tear down DDBLocal it'll kill the PID for the script, which will orphan the actual Java process and result in a hang.

I was able to temporarily work around this (until I can submit a pull request for said company build tool) by running this in the afterAll of my tests:

afterAll(() => {
    exec("kill -9 $(pgrep -f DynamoDBLocal)");
});

This being said project maintainers could probably close out this issue. I wasn't able to reproduce it in any other way and even if there's a hack fix it should probably be in the dynamodb-local project, not here.