-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Running the tests on a vanilla fork fails #9539
Comments
Hi @carlosduclos, thanks for the issue. It looks like there's not enough information for us to know how to help you. If you're reporting a bug, please be sure to include:
Requesting a new rule? Please see Proposing a New Rule for instructions. Requesting a rule change? Please see Proposing a Rule Change for instructions. If it's something else, please just provide as much additional information as possible. Thanks! |
npm install
npm test
|
@carlosduclos Are you running this on Windows or Mac/Linux? |
This issue was also noticed in #9542 (comment), so the build is failing on master too. At first glance, it looks like this was caused by the latest I think the correct fix is for us to remove all the tests that are currently failing, since they're not valid JavaScript. |
This corrects some tests which used `super` in an invalid way, and are now failing due to an acorn upgrade.
This corrects some tests which used `super` in an invalid way, and are now failing due to an acorn upgrade.
I ran this on Linux, Elementary Linux 04 (based on Ubuntu 16.04) |
@carlosduclos This issue has been fixed. It was caused by upgrade of Acorn library that started flagging some improper use of |
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
npm test
What did you expect to happen?
What actually happened? Please include the actual, raw output from ESLint.
The text was updated successfully, but these errors were encountered: