09 10 2017 22:52:13.289:INFO : Custom Starting browser ChromeHeadless 09 10 2017 22:52:13.283:INFO : Launching browser ChromeHeadless with unlimited concurrency All options you have given are handled by karma-chrome-launcher line 168 in "node_modules/karma-chrome-launcher/index.js" Im not using any custom launcher configurations. I can successfully run my tests without puppeteer. Did you report this to google chrome is not mandatory for ChromeHeadless browser in Karma. When logs start flushing from HeadlessChrome 0.0.0 Google chromeheadless stated its execution, means Karma-chrome-launcher is fine. it should launch "ChromeHeadless" Check my log below (mine is OSX as well, not Linux). Is there a fix or workaround for this issue? Is there a reason why it's not working on the Linux server [Ubuntu Server 14.04.5 The launcher is starting incorrect browser "Starting browser Chrome". I tried other flags like " -no-sandbox", " -disable-web-security" as suggested on a bunch of issues on karma repo. Without a remote debugging port, Google Chrome exits immediately. Const ChromiumRevision = require('puppeteer/package.json').puppeteer.chromium_revision Ĭonst Downloader = require('puppeteer/utils/ChromiumDownloader') Ĭonst revisionInfo = Downloader.revisionInfo(Downloader.currentPlatform(), ChromiumRevision)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |