$ cross-env TEST_ENV=1 ELECTRON_NO_ATTACH_CONSOLE=1 xvfb-maybe --auto-servernum -- jest --config ./app/jest.integration.config.js
FAIL app/test/integration/launch-test.ts (12.399s)
  App
    ✕ opens a window on launch (10008ms)
  ● App › opens a window on launch
    Timeout - Async callback was not invoked within the 10000ms timeout specified by jest.setTimeout.
      at mapper (../node_modules/jest-jasmine2/build/queue_runner.js:41:52)
  ● App › opens a window on launch
    TypeError: Cannot read property 'isVisible' of undefined
      40 | 
      41 |   it('opens a window on launch', async () => {
    > 42 |     await app.client.waitUntil(() => app.browserWindow.isVisible(), 5000)
         |                                                        ^
      43 | 
      44 |     const count = await app.client.getWindowCount()
      45 |     expect(count).toBe(1)
      at Object.app.client.waitUntil (test/integration/launch-test.ts:42:56)
      at Timer.tick (../node_modules/webdriverio/build/lib/utils/Timer.js:111:31)
      at Timer.start (../node_modules/webdriverio/build/lib/utils/Timer.js:75:22)
      at new Timer (../node_modules/webdriverio/build/lib/utils/Timer.js:62:14)
      at Object.<anonymous>.exports.default (../node_modules/webdriverio/build/lib/commands/waitUntil.js:25:17)
      at Object.exec (../node_modules/webdriverio/build/lib/helpers/safeExecute.js:28:24)
      at Object.resolve (../node_modules/webdriverio/build/lib/webdriverio.js:190:29)
      at lastPromise.then.resolve.call.depth (../node_modules/webdriverio/build/lib/webdriverio.js:485:32)
      at _fulfilled (../node_modules/q/q.js:854:54)
      at self.promiseDispatch.done (../node_modules/q/q.js:883:30)
      at Promise.promise.promiseDispatch (../node_modules/q/q.js:816:13)
      at ../node_modules/q/q.js:570:49
      at runSingle (../node_modules/q/q.js:137:13)
      at flush (../node_modules/q/q.js:125:13)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        12.976s
Ran all test suites.

Jest did not exit one second after the test run has completed.
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated