Latest version locking up!

[billnbell]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

See https://github.com/vercel/next.js/issues/45508#issuecomment-1574010754

Which area(s) of Next.js are affected? (leave empty if unsure)

Jest (next/jest)

Link to the code that reproduces this issue or a replay of the bug

#45508 (comment)

To Reproduce

See #45508 (comment)

Describe the Bug

#45508 (comment)

Expected Behavior

#45508 (comment)

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[BuddhiAbeyratne]

Suggest adding this at the end of build scripts for now

Please note this jest process is required and if you run this command you should pm2 restart so it makes the appropriate amount of workers
#45508 (comment)

[shuding]

Let's keep the conversation in that existing issue instead of having a new one, this doesn't help solving the problem but makes it harder for the team to track. Thanks!

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.