-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Watch mode throws error. #14172
Comments
Could it be that you are hitting #14046? |
Yes, that's it! I removed sl package and watch mode now works. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
Wow, I'm so lucky I ran across this! I installed |
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. |
Version
29.5.0
Steps to reproduce
Expected behavior
Should start watch mode with "No tests found"
Actual behavior
Additional context
The very same happens when running
./node_modules/jest/bin/jest.js --onlyChanged
When I add current directory ".",
./node_modules/jest/bin/jest.js . --onlyChanged
seems to work, but./node_modules/jest/bin/jest.js . --watch
starts the watch mode correctly but then after few seconds gives me the very same error.This issue is not present in jest 28, where it tells me it needs git repository and with initialized git repository it works. Initialized git repository seems to make no difference with 29. Presence/absence of test suites also seems to make no difference.
Environment
System: OS: Linux 5.4 Ubuntu 20.04.6 LTS (Focal Fossa) CPU: (4) x64 Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz Binaries: Node: 18.16.0 - /usr/bin/node npm: 9.5.1 - /usr/bin/npm npmPackages: jest: ^29.5.0 => 29.5.0
The text was updated successfully, but these errors were encountered: