[Tests] JS tests on Travis CI hang after completion

[ide]

It appears likely to be related to the Haste 2 change (cc @cpojer). The JS, CLI, and packager tests all run Jest and terminate with:

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

https://travis-ci.org/facebook/react-native/builds/110065663

This is the build log, which makes me think something in Haste 2 is the cause:

[cpojer]

Yeah it is likely haste 2 and file watching. Pretty sure it is one of these two: https://github.com/facebook/jest/blob/master/src/resolvers/HasteResolver.js#L117 – maybe persisting the cache or for some reason it can't stop watching the file system?

Can you somehow trigger a run just without properly ending either of these?

[skevy]

@cpojer I'm pretty sure it does have to do with the filewatcher...I encountered this when I was using node-haste elsewhere. I had to explicitly call .end() which is something we're probably not doing in these tests anywhere.

[cpojer]

ohhhhh... I noticed this in Jest too when I was creating a real FileWatcher instance in one of my tests and then I didn't kill that one. Are we doing this anywhere in the tests for react-native? Like, create an unmocked instance of FileWatcher that we don't call .end() on?

[cpojer]

Ide, this is fixed now, right? Feel free to reopen if its still an issue.

[ide]

LGTM, tests are failing instead of erroring so that's good.

[a7ul]

Hi, We are getting this same issue on travis now.
We are using "jest": "^19.0.2"
Any solution or
workaround ?

It works fine on local . Only on travis it just hangs