MacOS: Jest does not exit any more due to fsevents update

[kryops]

🐛 Bug Report

Jest does not exit any longer after the tests are done on MacOS.

I tracked it down to the Update of fsevents@2.2.0. Not sure if it might be better to open an issue there, or if you can fix it on your end. (Edit: I created fsevents/fsevents#345)

As a workaround, I added the following to my package.json (through yarn):

"resolutions": {
  "**/jest-haste-map/fsevents": "2.1.3"
}

(Edit: Note that this workaround will fail installing on Windows and Linux. If you have a lock file (yarn.lock or package-lock.json), you should be able to set the version of fsevents to 2.1.3 there, see #10777 (comment) below)

To Reproduce

Steps to reproduce the behavior:

Just run jest - I could reproduce it in a minimal repository with just Jest and a single test file.

package.json

{
  "name": "foo",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "test": "jest"
  },
  "dependencies": {
    "jest": "^26.6.2"
  }
}

foo.test.js

describe('test', () => {
  it('test', () => {
    expect(true).toBe(true)
  })
})

Expected behavior

Jest should exit after the tests are done.

envinfo

  System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
  Binaries:
    Node: 12.16.3 - ~/.nvm/versions/node/v12.16.3/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v12.16.3/bin/npm
  npmPackages:
    jest: ^26.6.2 => 26.6.2 

I also reproduced this on Node 14.1.0 and 15.0.1

[Chriscbr]

I believe I'm getting the same issue. I tried upgrading all kinds of dependencies/tools to see if any of that would fix it (along with trying other suggestions found around the net to fix hanging tests, such as uninstalling/reinstalling watchman on homebrew), but had no luck. I was wondering if it was some issue with a new version of jest, but the newest version I could find that doesn't hang out of the box was v24.9.0, which is pretty old at this point.

  System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  Binaries:
    Node: 14.15.0 - ~/.nvm/versions/node/v14.15.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.8 - ~/.nvm/versions/node/v14.15.0/bin/npm
  npmPackages:
    jest: ^26.6.2 => 26.6.2

Thanks for the workaround @kryops 👍

[shian15810]

Confirmed getting this on macOS, and @kryops temporary workaround solved this. Thanks!

I think this issue is ultimately related to another issue about --detectOpenHandles: #9473

[michaelbrewer]

Same here. Broken on macOS

[adamgruber]

FWIW, if you can downgrade to node 10, that also seems to provide a temporary workaround.

[SimenB]

Reporting to fsevents seems like a good idea. I haven't investigated on our side, but I don't think we do anything weird.

EDIT: In case people miss the link below: fsevents/fsevents#345

[pkibbey]

After hitting these same issues all day... I upgraded jest to 26.6.3.

My tests are now exiting without the need for --forceExit, or any other workaround.