Chrome not captured when running tests on Travis
See original GitHub issueKarma 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: https://github.com/travis-ci/travis-ci/issues/2555
Issue Analytics
- State:
- Created 9 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
How to put Angular unit tests with Travis (No captured browser)?
I solved this issue. I just changed export CHROME_BIN=usr/bin/google-chrome in .travils.yml by export CHROME_BIN=chromium-browser, ...
Read more >GUI and Headless Browser Testing - Travis CI Docs
To run tests requiring a graphical user interface on Travis CI, use xvfb (X Virtual Framebuffer) to imitate a display. If you need...
Read more >Problems with Karma and Chrome - Travis CI Community
The tests run fine locally and I have added the --no-sandbox flag to the launcher in Karma. What else can it be? native-api ......
Read more >Running Jasmine Tests in Google Chrome on Travis CI
This article gives a short introduction to running Jasmine tests (based on jQuery) in Google Chrome on Travis CI (through GitHub).
Read more >Running Travis CI Unit Tests Using Google Chrome - 500Tech
Setting up Travis to work with PhantomJS is easy and fast however it makes more sense to run tests against a browser your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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
@MrOrz Thanks! The no-sandbox flag was missing. 😃