Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bumping jest from 26.6.2 to 26.6.3 causes test running to never terminate #10855

Closed
heath-freenome opened this issue Nov 20, 2020 · 4 comments
Closed

Comments

@heath-freenome
Copy link

馃挜 Regression Report

Last working version

Worked up to version: 26.6.2

Stopped working in version: 26.6.3

To Reproduce

Steps to reproduce the behavior:

Clone this repo, do npm ci then npm run test and watch the test stay running until CTRL-C is used

Expected behavior

npm run test will run the test then return the user to the command prompt

Link to repl or repo (highly encouraged)

https://github.com/heath-freenome/busted-jest

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: macOS 10.15.7
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 14.7.0 - ~/.nvm/versions/node/v14.7.0/bin/node
    npm: 6.14.7 - ~/.nvm/versions/node/v14.7.0/bin/npm
  npmPackages:
    jest: ^26.6.3 => 26.6.3 
@leonardopliski
Copy link

Try to add the fsevents package 2.2.1 version temporarily with:

npm i -D fsevents@2.2.1

#10777 and #9473 seems to be related.

@SimenB
Copy link
Member

SimenB commented Dec 8, 2020

Yep, this is a duplicate of ##10777. Either upgrade or downgrade the installed version of fsevents

@SimenB SimenB closed this as completed Dec 8, 2020
@heath-freenome
Copy link
Author

heath-freenome commented Dec 11, 2020

I fixed this issue by uninstalling and reinstalling jest@26.6.3 using npm. Not sure how it got messed up in the first place. The resulting reinstall included fsevents@2.2.1. For whatever reason the other suggestion of deleting node_modules and rerunning npm install didn't work. Thanks for the pointers

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants