-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
"yarn test" in master branch fails on new installation #9015
Comments
I can reproduce this error on warm and cold eslint cache:
Not sure why it differs from the CI. I'm curious though, how you manage to run yarn 1.19, when we explicitly set |
I thought that yarn version was the reason, so I upgraded it. Nevertheless, with 1.17 everything is the same on both systems. Just now reverted back to 1.17 and tested again. |
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. |
🐛 Bug Report
I just wanted to contribute. Followed the guide, and got:
To make sure that it is not my fault, I repeated the same with other system, and got:
So, as we can see, errors occur in different files, but in both cases they are linked to eslint. Maybe need to use specific version? Again - I did not made any changes in both cases, strictly following the given scenario.
To Reproduce
Steps to reproduce the behavior:
Just follow this guide from scratch - https://github.com/facebook/jest/blob/master/CONTRIBUTING.md
(I did this on two different systems and got eslint errors in both cases)
Expected behavior
"yarn test" should work without errors.
envinfo
System:
OS: macOS 10.14.6
CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
Binaries:
Node: 10.16.3 - /usr/local/bin/node
Yarn: 1.19.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
System:
OS: Linux 4.15 Ubuntu 16.04.6 LTS (Xenial Xerus)
CPU: (1) x64 Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz
Binaries:
Node: 11.14.0 - /usr/bin/node
Yarn: 1.19.0 - /usr/bin/yarn
npm: 6.9.2 - /usr/bin/npm
The text was updated successfully, but these errors were encountered: