Having problems running karma with jenkins in chrome
See original GitHub issueAfter chrome updated today it seems our builds no longer work. interactive shells seem to work, just not in jenkins 😦
chrome Version 52.0.2743.82 m OS: Windows Server 2012 r2
[4mRunning "karma:continuous" (karma) task[24m
[32mINFO [karma]: [39mKarma v0.12.31 server started at http://localhost:9876/
[32mINFO [launcher]: [39mStarting browser Chrome
[32mINFO [framework.browserify]: [39m2640391 bytes written (24.08 seconds)
[32mINFO [framework.browserify]: [39mbundle built
[33mWARN [launcher]: [39mChrome have not captured in 60000 ms, killing.
[32mINFO [launcher]: [39mTrying to start Chrome again (1/2).
[33mWARN [launcher]: [39mChrome have not captured in 60000 ms, killing.
[32mINFO [launcher]: [39mTrying to start Chrome again (2/2).
[33mWARN [launcher]: [39mChrome have not captured in 60000 ms, killing.
[31mERROR [launcher]: [39mChrome failed 2 times (timeout). Giving up.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:6
- Comments:44
Top Results From Across the Web
Karma Chrome Headless not working on Jenkins
Based on issue Karma 1.6 breaks Headless support for Chrome created on github, it is related to the slower machine and happens, ...
Read more >Jenkins + karma + Chrome not working after last update
INFO [launcher]: Trying to start Chrome again (1/2). WARN [launcher]: Chrome have not captured in 60000 ms, killing. INFO [launcher]: Trying to start...
Read more >Karma test with ChromeHeadless '--no-sandbox' issue
I'm trying to run Karma tests in Jenkins pipeline. I'm new to this topic, and to start, I pulled openui5-sample-app from Git repository....
Read more >karma-runner - Bountysource
When launching the karma test with chrome already running, three karma tabs open, connect, lose the connection again and then karma crashes.
Read more >Troubleshooting - Karma test runner
The --no-single-run option causes the server to print a URL and wait. Open the URL in a browser and use the browsers devtools...
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 was running into the same issue with both e2e protractor tests and Karma unit tests. Windows jenkins specifically (running manually in cmd was working fine).
The (temp) fix was the same for both:
In karma.conf:
In protractor.conf
“karma-chrome-launcher”: “^1.0.1”, and “protractor”: “4.0.0”,
Same problem for me with the following setup:
karma-chrome-launcher: 2.0.0 karma: 1.3.0 chrome: 53.0.2785.116 os: CentOS 7