Jest without --runInBand slow under Travis

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Tests run fine locally or with -i under travis. However running without -i in travis, tests take much longer (timing out).

If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.

• Locally tests (with --ci) take Time: 7.319s, estimated 8s
• Locally with --ci -i tests take Time: 16.517s, estimated 21s
• Tests on travis-ci with -i completes in 67 seconds: https://travis-ci.org/fengari-lua/fengari/jobs/366723336#L378
• Tests on travis-ci without -i take over 20 minutes and travis-ci times out: https://travis-ci.org/fengari-lua/fengari/jobs/366419164#L540

What is the expected behavior?

Tests shouldn’t take > 20 minutes to run under travis when they take < 10 seconds locally.

Please provide your exact Jest configuration

No configuration. See repository for any details. https://github.com/fengari-lua/fengari/compare/v0.1.1...ebf18e2

Run npx envinfo --preset jest in your project directory and paste the results here

I don’t think this is the output you wanted…

$ npx envinfo --preset jest
npx: installed 1 in 1.326s
(node:11650) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '1' of null
    at e.darwin.process.platform.linux.process.platform.c.run.then.e (/home/daurnimator/.npm/_npx/11650/lib/node_modules/envinfo/dist/cli.js:2:94055)
    at <anonymous>
(node:11650) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:11650) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[philvarner]

It would nice if this were in the jest documentation as a behavior of CircleCI. I was getting the Error: spawn ENOMEM failures in CircleCI, but not locally, and the fix of running jest --maxWorkers=2 worked perfectly, but it look almost an hour for me to figure that out, and the suggestion to add that flag that is buried deep in another (closed) bug about the memory problems.

[daurnimator]

I think this can be closed now.

How so? It wasn’t fixed.