Headless Chrome times out without executing any tests

I have configured the headless chrome in my project getting rid of Phantom. When I run the tests on my OSX machine, all the tests get executed with the test runner on the headless chrome. But the same doesn't happen on my linux server. It connects to the socket and then after some time, it disconnects and shows the error message saying "Karma tests failed". Error: ``` 25 09 2017 13:56:19.075:INFO [karma]: Karma v1.5.0 server started at http://0.0.0.0:9876/build/ 25 09 2017 13:56:19.076:INFO [launcher]: Launching browser ChromeHeadless with unlimited concurrency 25 09 2017 13:56:19.080:INFO [launcher]: Starting browser Chrome 25 09 2017 13:56:19.263:INFO [HeadlessChrome 0.0.0 (Linux 0.0.0)]: Connected on socket zDM7md2A7Je8kqsPAAAA with id 1679961 25 09 2017 13:58:19.552:WARN [HeadlessChrome 0.0.0 (Linux 0.0.0)]: Disconnected (1 times), because no message in 120000 ms. HeadlessChrome 0.0.0 (Linux 0.0.0) ERROR Disconnected, because no message in 120000 ms. ``` Here is my configuration: ``` const ChromiumRevision = require('puppeteer/package.json').puppeteer.chromium_revision; const Downloader = require('puppeteer/utils/ChromiumDownloader'); const revisionInfo = Downloader.revisionInfo(Downloader.currentPlatform(), ChromiumRevision); process.env.CHROME_BIN = revisionInfo.executablePath; module.exports = function (config) { config.set({ basePath: 'build/', frameworks: ['jasmine'], plugins: [ require('karma-jasmine'), requi

Posted by applecool on Sep 25, 2017, 9:37 PM

Tags

• github (Sysadmin)

Related issues

• Custom games stuck on "finding server" for all european servers
• Feature request: add ACP (Agent Client Protocol) stdio JSON-RPC mode
• Forza Horizon 6 (2483190)
• Turn off integrated browser for default
• Weekly updates are too frequent
• [BUG] Max 20x plan: 100% usage after 2 hours of light work (5 commits, no agents)