Travis Node v4.0.0 and v4.1.0: A worker process has quit unexpectedly

[homer0]

I'm trying to run my project tests on Travis-ci but I keep getting random failures with the following message:

Running 9 test suites...A worker process has quit unexpectedly! Most likely this an initialization error.
npm ERR! Test failed.  See above for more details.

The suite has 19 tests, and sometimes it stops in the middle of the suite and throws the error. Everything seems to be working just fine on my mac (node v4.0.0) so I'm assuming it's an issue with Travis.

Here's my .travis.yml file (the compiler options are for node-gyp):

language: node_js
env:
  - CXX=g++-4.8
addons:
  apt:
    sources:
    - ubuntu-toolchain-r-test
    packages:
    - g++-4.8
node_js:
  - "4.1"
  - "4.0"
before_install:
  npm i npm@2.14.4 --global
before_script:
  npm rebuild
after_success:
  - 'cat ./coverage/lcov.info | ./node_modules/.bin/coveralls'

I even set the concurrent jobs to 1, not sure if that can affect (sometimes one fails and the other pass). Any ideas?

Thanks.

[cpojer]

Which version of jest are you using? There must be something bad going on in one of your tests. Have you been able to isolate which test is throwing up?

[homer0]

@cpojer Sorry, I forgot to mention, I'm using the latest (v0.7.1). Here's my project: https://github.com/Olapic/DevKit-ES6, and I'm using this PR to test all the possible solutions.
Regarding a specific test, I tried removing some cases from the file it stopped the first time, but it's totally random (sometimes it fails at the third file, others at the fifth and sometimes at the evelenth).

Thanks

[cpojer]

Can you try to disable coverage and see if it stops reproing?

The list of tests being reported is misleading because it fails to run certain tests. So it would be good to know which tests always pass and whether it is always the same test that causes the crash.

[homer0]

I just disabled the coverage and pushed it. I think this url so you can see the output.
And I'll try to make a list of tests that always pass.

Thanks

[homer0]

@cpojer It worked, I disabled the coverage and tests passed. So it seems like this an issue from istanbul right?

[cpojer]

Yeah, coverage is a little bit flaky unfortunately. If you have time to look into this, I would suggest forking jest and upgrading istanbul and see if the issue goes away.

[homer0]

@cpojer Sorry I didn't reply before; I re enabled the coverage, but I set the collectCoverageOnlyFrom, from that point, it only failed once in 8 runs, but I re tried the build and it passed.

if I have a time today, I'll fork it and try the latest version of istanbul and let you know.

Thanks!

[homer0]

Closing this since it's not directly related to Jest but rather one of the dependencies.

[github-actions]

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.