Disable coverage on Travis

[sophiebits]

cc @zpao

[zpao]

It doesn't look like it worked… but do whatever it takes

[ghost]

@spicyj updated the pull request.

[gaearon]

It used to work 😞 What happened?

[sophiebits]

¯_(ツ)_/¯ want to dig into it?

[keyz]

Last time I checked, the ./coverage folder contains nothing after running grunt jest:coverage. But jest --coverage works. Could it be a grunt script related issue? It might be related to jestjs/jest#433

[keyz]

Looking at travis logs, it seems that the coverage stopped working after #6620.
If I remove '--runInBand' from our grunt task then it generates coverage correctly. Am I on the right path @zpao @cpojer? :)

[sophiebits]

That sounds believable. I think not using runInBand was making the tests flakier. Maybe because of the extra memory overhead? Not sure. So the issue is that jest might not support coverage with runInBand properly. I haven't looked into it at all, but that might not be too hard to fix.

[keyz]

Yeah, Jest doesn't generate coverage when used with runInBand.

[cpojer]

That is weird and seems like a bug in Jest. It is probably a silly thing that's easy to fix.

[zpao]

Going to bring this over to 15-stable. We already don't run coverage there but want to try to keep these in sync.