error: (CC::Analyzer::Engine::EngineFailure) engine eslint failed with status 139 and stderr "" about codeclimate-eslint HOT 17 CLOSED

I have also experienced this issue.

from codeclimate-eslint.

Hi, from what I can tell, this (and another I've seen, status 138) are out-of-memory scenarios.

Are these large repos you're analyzing? If so, could you try cutting down the number of source files via exclude_paths?

from codeclimate-eslint.

I'm unsure why, but exclude_paths doesn't seem to work for me. My db folder still gets analysed by Rubocop. ESlint is probably going through all of the bower_components and node_modules 😦

from codeclimate-eslint.

Can I see your codeclimate.yml? Specifically, I'm thinking exclude_paths: db won't work, and you need exclude_paths: db/**/*. If that's the case, we should improve the docs in this regard.

from codeclimate-eslint.

I don't have the .codeclimate.yml file any more, unfortunately, and I never committed it because I didn't want to share it unless I had it working. I don't believe I used quotes around the path (like http://docs.codeclimate.com/article/289-configuring-your-repository-via-codeclimate-yml shows), if that has any relevance. I definitely did use the **/* pattern..

from codeclimate-eslint.

I'm running to this as well. It seems that exclude_paths aren't being respected by eslint (possibly due to different formats). I'm running this in an ember app, and had to remove tmp, dist, node_modules, and bower_components to get codeclimate analyze to run.

from codeclimate-eslint.

@tim-evans what version of the CLI are you running? You can find that by running codeclimate version

from codeclimate-eslint.

@gordondiggs 0.0.25

from codeclimate-eslint.

@tim-evans thanks - can you post the .codeclimate.yml file you are using?

from codeclimate-eslint.

Sure!

---
engines:
  eslint:
    enabled: true
  fixme:
    enabled: true
  watson:
    enabled: true
ratings:
  paths:
  - "app/**"
  - "addon/**"
  - "blueprints/**"
exclude_paths:
- config/**
- dist/**
- vendor/**
- node_modules/**
- bower_components/**
- tmp/**

The repository that I'm working on is: https://github.com/paddle8/ember-plupload

If you npm install and bower install, then try to run codeclimate analyze, the problem should appear.

from codeclimate-eslint.

knownasilya/ember-plupload#31

from codeclimate-eslint.

Thanks @gordondiggs I'm working through this with @ABaldwinHunter right now and we're trying to ignore blueprints/file-filter/files/app/file-filters/__name__.js from analysis.

We've added the full path to .codeclimate.yml, but couldn't get rid of the warning. It seems like patterns in the exclude_paths aren't being respected by eslint.

from codeclimate-eslint.

@tim-evans I just pushed a new version of the image that changes the way we handle exclude patterns - is it better after you update?

from codeclimate-eslint.

@gordondiggs still having trouble. Running codeclimate analyze on the addon repo after calling bower install / npm install still takes a long time.

I'm running codeclimate v 0.1.5 now.

from codeclimate-eslint.

Hi @jcope2013 @liamdawson @tim-evans,

Are you still experiencing this issue? We made improvements to workspace calculation in codeclimate/codeclimate#308 which may have had an impact.

Let us know either way. Thanks!

from codeclimate-eslint.

I'm going to close this issue for now. Feel free to reopen if this is still occurring.

from codeclimate-eslint.