-
-
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
Tests not running #2219
Comments
Hi @zigomir, this seems like an issue with If that not helps, could you please try installing your deps with other version of npm, e.g. using |
I tried |
This is strange. I can still run tests, and they pass when fixing the error, using the same Node version, using either Yarn or npm. Which OS are you on? Have you tried on other machine? |
Huh, this is strange. Running now on my VM (Debian) it runs, but not on my host, macOS v10.12.1 :/ |
I use the same macOS and it works, so this definitely has to be something with your environment. Maybe try to reinstall Node, remove node_modules? It sometimes does the trick ^^ |
Closing to manage the queue but happy to keep the discussion going and reopen if necessary. |
I figured out jest won't run if i have I was able to find this out running Can you please check if this is the case, I see https://github.com/facebook/watchman is Facebook's repo too ;) |
I have watchman installed too (v4.5.0). Probably there was an issue with the version you've been using. Would be great if you installed newer version and try it once more :) |
Of course I tried that first. It didn't help. I have a version v4.7.0 installed now and jest won't run. |
Check out the bottom of this thread, might be related: #1767 |
Thanks @cpojer! Yeah this is certainly related to my issue. So stopping watchman with |
Another Mac OS user here that got bit by this issue, uninstalling |
Yet another watchman victim, thought for sure I messed up the babel and webpack configuration. Uninstall and all is well. |
Yes, |
An easy solution to run the tests is with |
Another victim of watchman here :( |
i have the same issue it work with yarn test --u --no-watchman |
Upgrading to latest watchman (4.9) worked for me. |
According to jestjs/jest#2219, jest will not run tests if watchman is installed. It is not entirely clear if this is the case in our OSX CI environment, but the symptoms seem close to what's reported in the issue. Possible fix for https://github.com/aspnet/AspNetCore-Internal/issues/1619
According to jestjs/jest#2219, jest will not run tests if watchman is installed. It is not entirely clear if this is the case in our OSX CI environment, but the symptoms seem close to what's reported in the issue. Possible fix for https://github.com/aspnet/AspNetCore-Internal/issues/1619
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. |
I went through getting started but can't get jest to work. I use node v6.9.1, npm v3.10.8 and jest v17.0.3. I also tried
--no-cache
and--debug
but nothing changes. I even moved test to__tests__
dir and renamed it accordingly.Do you want to request a feature or report a bug?
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal repository on GitHub that we can
npm install
andnpm test
.https://github.com/zigomir/jester
What is the expected behavior?
Test running and passing.
Run Jest again with
--debug
and provide the full configuration it prints. Please mention your node and npm version and operating system.Still nothing.
The text was updated successfully, but these errors were encountered: