Chrome not captured when running tests on Travis

[justinmanley]

Karma tests are failing on Travis when it tries to run tests in Chrome.

Since I posted this issue on the travis-ci issues page, I've noticed that the tests run successfully in PhantomJS, so I'm wondering if this error may be traced back to Karma.

The error message is:

INFO [launcher]: Starting browser Chrome
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
INFO [launcher]: Trying to start Chrome again (1/2).
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
INFO [launcher]: Trying to start Chrome again (2/2).
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
ERROR [launcher]: Chrome failed 2 times (timeout). Giving up.

Detailed issue report here: travis-ci/travis-ci#2555

[pkozlowski-opensource]

@manleyjster AFAIK Travis-CI VMs don't have Chrome installed, by default only FFox is present. You could use this one but in this case you need to add

  - "export DISPLAY=:99.0"
  - "sh -e /etc/init.d/xvfb start"

to your TravisCI install as explained here: http://docs.travis-ci.com/user/gui-and-headless-browsers/

Closing as this is an issue with what TravisCI provides and not a bug in Karma. If you want to test on multiple browsers you could use services like SaucLabs or similar.

[justinmanley]

Thanks for responding - and thanks for the link to the GUI & Headless Browsers article - I hadn't seen that!

I take your point, but I still think it's possible that Karma is implicated in this issue.

If you look through my original issue report, you'll see that I was aware that Chrome is not installed by default on Travis CI and had added the following to my .travis.yml:

- wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
- sudo sh -c 'echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list'
- sudo apt-get update -qq
- sudo apt-get install -qq google-chrome-stable

At your suggestion (from above), I added:

- export DISPLAY=:0
- sh -e /etc/init.d/xvfb start

to my .travis.yml, but to no effect. As before, Karma started Chrome successfully, then failed to capture it: build 31091782.

Evidently it's more complicated than simply needing to start up the virtual X frame buffer.

[pkozlowski-opensource]

@manleyjster I'm just going over various issues on Travis-CI and people are reporting various things about being able to install & start chrome in the Travis VM. Did you try to verify that chrome actually starts properly after you install it?

I still believe that the issue you are facing is due to the chrome not being installed properly and I'm pretty positive that this is not Karma problem. But yes, could you try to add a command to your Travis-CI sript that would open chrome?

[henvic]

👍 same problem here.

[pkozlowski-opensource]

@henvic could you elaborate? Did you try to verify that Chrome is properly installed on Travis-CI and operational? From what I can see on various info on the net installing Chrome on Travis requires some mad science, ex.: https://twitter.com/domenic/status/502571560944021506

For now it still sounds like Chrome install problem on Travis but I don't have free cycles left to investigate it further. Although I would be interested in the solution :-)

[MrOrz]

I did not got Google Chrome running on Travis-CI either. It installs but we are not sure if it starts up.

I happened to got it running on using the Chromium pre-installed in the Travis-CI VM though, by setting CHROME_BIN, the frame-buffer things, and the --no-sandbox flag.

https://github.com/MrOrz/SeeSS/blob/master/.travis.yml
https://github.com/MrOrz/SeeSS/blob/master/test/karma.conf.js

Build log: https://travis-ci.org/MrOrz/SeeSS/builds/33732670

[janpaepke]

Thanks, MrOrz!
Your solution works! Awesome! :)

[djindjic]

👍 @MrOrz

[dignifiedquire]

Not an issue with karma, so closing.

[ghost]

@MrOrz Thanks! The no-sandbox flag was missing. :-)