Problems running chimpy on Gitlab `Error: unknown error: Chrome failed to start: exited abnormally` about chimpy

[thebarty]

YES! This one did the trick!!!!

The next issue just came up - chimp does NOT run all my tests. But it's my first iteration on CI and I'll try to figure it out… thanks for your help again!

[lucetius]

It looks like Chrome problem. Can you paste ./tests/_chimp_config.js file?

[thebarty]

@lucetius Thanks a lot for your help, man! I really appreciate it…

This is my ./tests/_chimp_config.js.

Do you need any more infos?

/**
 * Settings that are used in CircleCi to adapt Chimps behaviour.
 * For further possible settings look at the file
 *  https://github.com/xolvio/chimp/blob/master/src/bin/default.js
 */
module.exports = {
  // - - - - MOCHA  - - - -
  mochaCommandLineOptions: ['--color'],
  mochaConfig: {
    tags: '@pass1, @pass2, @pass3, @pass4, @pass5',  // tags and grep only work when watch mode is false
    grep: null,
    timeout: 120000,  // 2 minutes
    // reporter: 'spec',  // default only to console (WORKS, but does NOT output CircleCi-compatible data)
    reporter: 'mocha-circleci-reporter',  // default for CircleCi https://www.npmjs.com/package/mocha-circleci-reporter
    slow: 10000,
  },

  // - - - - WEBDRIVER-IO  - - - -
  webdriverio: {
    waitforTimeout: 10000, // time to wait until element appears.
                           // => p.e. for modals to appear, so make it quite long
                           // => default is 500
    waitforInterval: 250,  // KEEP SMALL (!!!) this is the INTERVAL in which waitFor* is looped for checks
  },

  // - - - - DEBUGGING  - - - -
  // log: 'info',
  // debug: true,
}

[lucetius]

Try to change webdriverio section to:

  // - - - - WEBDRIVER-IO  - - - -
  webdriverio: {
    desiredCapabilities: {
      browserName: 'chrome',
      chromeOptions: { args: ['--no-sandbox', '--headless'] },
    },
    waitforTimeout: 10000, // time to wait until element appears.
                           // => p.e. for modals to appear, so make it quite long
                           // => default is 500
    waitforInterval: 250,  // KEEP SMALL (!!!) this is the INTERVAL in which waitFor* is looped for checks
  },

in your ./tests/_chimp_config.js

[thebarty]

@lucetius I am seeing those errors in my tests. For some reasons chimpy does not seem to be able to connect to meteor. PLUS after only a few tests it exits.

Can you guide me to a best-practise example on how to setup chimpy with meteor on ci?

                 *   waiting for element to exist "div#__blaze-root"
stdout:                  *   waiting for element to exist "div#__blaze-root"
stderr: Unhandled rejection Error: connect ECONNREFUSED 127.0.0.1:3000
    at Object.exports._errnoException (util.js:1020:11)
    at exports._exceptionWithHostPort (util.js:1043:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)

[thebarty]

I've got it!

It was maxBuffer set too small when executing via child_process.exec().

See
meteor/todos#273
meteor/todos#274