Jest gets force exited when called via test:all

[trivikr]

Describe the bug

Jest shows the following message on running test:all

A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.

Test Suites: 2 skipped, 228 passed, 228 of 230 total
Tests:       20 skipped, 3641 passed, 3661 total
Snapshots:   0 total
Time:        29.497 s
Ran all test suites in 94 projects.

Your environment

SDK version number

main branch

Is the issue in the browser/Node.js/ReactNative?

Unit Testing

Details of the browser/Node.js/ReactNative version

N/A

Steps to reproduce

Run yarn test:all

Observed behavior

Jest gets force exited, but shows success.
This issue is not reproducible in CI though, checked in the latest run on main branch at sdk-staging-test:af48d0df-0b4f-4521-a939-7c39ba25442b

Expected behavior

Jest does not force exit

Additional context

This issue was noticed while debugging Jest Out of Memory error in #3149

[github-actions]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.