[Bug?]: Jest crashed in 3.2.0-rc (infinity loop)

[dobernike]

Self-service

• I'd be willing to implement a fix

Describe the bug

After I install yarn canary build (3.2.0-rc.15), I got infinity loop when I started jest.

Moved back to 3.1.1 and now everything right

Monorepo have package with "type: module"

and I use pnpEnableEsmLoader: true

For fixed it I used additional flags in jest: "jest --runInBand --detectOpenHandles --forceExit"

To reproduce

You need have jest and yarn berry, mb workspaces with cjs and esm packages

install yarn canary build - "yarn set version canary" (3.2.0-rc.15)
try to use jest

Environment

System:
    OS: macOS 12.1
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 14.19.0 - /private/var/folders/73/zstsh7455c9fjsv3t1g9_4vm0000gn/T/xfs-a4b22e0c/node
    Yarn: 3.2.0-rc.15 - /private/var/folders/73/zstsh7455c9fjsv3t1g9_4vm0000gn/T/xfs-a4b22e0c/yarn
    npm: 6.14.16 - /opt/homebrew/bin/npm

Additional context

[merceyz]

I'm guessing you're running into nodejs/node#41221, try updating to Node.js v16.14.0 or v17.4.0.

Without a reproduction that's just a guess though, please provide an actual reproduction that we can clone and run.

[arlyon]

I also have this issue, and node 16/17 don't resolve the issue. For a trivial repro:

$ mkdir -p test-test && cd jest-test
$ yarn init -2
$ yarn add jest
$ node --version
v17.6.0
$ yarn --version
3.2.0
$ yarn jest --passWithNoTests
^C% # hangs
$ yarn set version 3.1.1
$ yarn --version
3.1.1
$ yarn jest --passWithNoTests
No tests found, exiting with code 0

I am on Fedora 35, if that makes a difference.

[stefpb]

We have the this issue: The command yarn test is stucked with no output. Downgrade to yarn@3.1.1 helps.

[protyze]

I'm guessing you're running into nodejs/node#41221, try updating to Node.js v16.14.0 or v17.4.0.

Without a reproduction that's just a guess though, please provide an actual reproduction that we can clone and run.

Ran into the same issue --> upgrading to node.js v16.14.0 (from 16.13.x) fixed it for me.

[darthtrevino]

I'm using jest --runInBand as a workaround

[yarnbot]

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟