The text was updated successfully, but these errors were encountered: Tried with the above suggestion, still i am getting the same error. ['ChromeHeadless'] in the Karma config file. I created a Karma framework type plugin that does just that. @swetapatil1 try npm i --save-dev puppeteer to get ChromeHeadless working. Asking for help, clarification, or responding to other answers. Other issues can be directly viewed from the launcher source code, and may be faster than Google, which is relatively simple. mocha, Mocha is a javascrip Record the problems, causes, and solutions in the corresponding scenarios of Kafka. I actually didn't need any of this when running an ubuntu base. @cmacdonnacha O'rly. You signed in with another tab or window. 06 11 2017 13:18:08.774:WARN [launcher]: Chrome have not captured in 60000 ms, killing. In addition,browsers: ['Chrome']withbrowsers: ['ChromeHeadless']The difference is: ChromeHeadless is a pop-up mode. Flutter change focus color and icon color but not works. Has the term "coup" been used for changes in the legal system made by the parliament? If you want to run automated tests using Headless Chrome, look no further! Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! By clicking Post Your Answer, you agree to our terms of service, privacy policy and cookie policy. Currently, Puppeteer has an issue with Karma on Linux machines, see GitHub issue @applecool FWIW we have a working Linux Mint (Ubuntu) and Alpine config using puppeteer, which I'll post here if it might help at all. Why can't I start? I wrote up a bug for Angular CLI for this as well: https://github.com/angular/angular-cli/issues/20449. libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-xcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libx I created a Karma framework type plugin that does just that. (like this question) but then will run the unit tests just fine. Sorry, should have mentioned that. I have exact issue - I cannot run my configuration on GitLab CI. For the ones that experience this issue with Angular. I remove puppateer from my packages.json file. Open Debug to see the command line started by Chrome. [launcher]: Starting browser ChromeHeadless 19 03 2021 11:27:19.268:WARN [launcher]: ChromeHeadless have not captured in 60000 ms, killing. Already on GitHub? I am expecting the tests to run successfully in all three instances (local npm, local Gitlab Runner and remote Gitlab CI/CD pipeline). chromeheadless have not captured in 60000 ms, killing. Hello guys I tried everything but not a single thing worked for me. And I have also tried on the Linux GUI (Ubuntu Desktop 16.0.4 LTS). This may have been an issue with the specific @angular/core version (v11.1.1), or with my Angular package versions not matching. Unfortunately, the error still persists with Chrome Headless 89.0.4389.82. You can try by commenting window.location.href. unread, My Azure pipeline always chirps with one ChromeHeadless have not captured in 60000 ms, killing. Not able to make karma work. If this is not working for you please comment. tl;dr: make sure you kill any servers running locally on your karma server's port (usually 8080). captureTimeout:120000default 60000 browsers: ['Chrome']browsers: ['ChromeHeadless']ChromeHeadless BrowserChromeHeadless_test Is there a fix or workaround for this issue? The workaround using --source-map=false is just putting less stress on the system. --remote-debugging-port=9222 \. Angular Karma - Chrome have not captured in 60000 ms . . rev2023.3.1.43269. The text was updated successfully, but these errors were encountered: I faced the same issue. Thanks for pointing this out: Starting browser Chrome. solved by this #154 (comment), I resolved it by changing the version of Socket from 3.x to 2.x. Couldn't it be puppeteer issue? I was using node:10.16.0-alpine and chrome was crashing because a bunch of stuff it needs didn't come in that image by default. It just times out. I definitely needed the --no-sandbox flag, and I needed to set the CHROME_BIN env var in my karma config, but the thing that really tripped me up turned out to be missing dependencies for chrome in my docker image. Indeed compilating the complete SCSS file for the Kendo theme will cause an Angular project to take some more time to compile the complete SCSS file. After testing with Firefox, it had the same result. If any browser does not get captured within the timeout, Karma will kill it and try to launch it again and, after three attempts to capture it, Karma will give up. ERROR [launcher]: Chrome failed 2 times (timeout). Does Cast a Spell make you a spellcaster? Not the answer you're looking for? Ran into this same problem and commenting out window.location.href = allows all tests to run to completion consistently. To do that, create a customLaunchers field that extends the base ChromeHeadless launcher: Configuring Karma to run your tests in Headless Chrome is the hard part. What could be done to avoid that is to load the SCSS files per component as demonstrated in the following article: https://www.telerik.com/kendo-angular-ui/components/styling/custom-themes/#toc-using-the-build-process-of-the-application. Thanks! The text was updated successfully, but these errors were encountered: Looks like the issue arise only when installing puppeteer locally to the project (meaning it's inside the package.json dev dependencies), compared to installed globally. The workaround posted by @andrewl-telnyx appears to be working for me. To learn more, see our tips on writing great answers. If you want, this is my configuration for karma and docker and it works: @jmaitrehenry Can I have a look at your package.json file? Default: 60000. . This worked for me, Also adding --no-sandbox to the flag list helps. @doroncy From what I remember, if I had errors in my unit tests (I think I had syntax errors), then I was getting the ChromeHeadless failed error without any indication of the syntax errors. Puede aumentar el tiempo de inicio de esta manera: captureTimeout:120000 default 60000. By clicking Sign up for GitHub, you agree to our terms of service and @NealAJohnson do you know how to make it to be waiting? ChromeHeadless have not captured in 60000 ms, killing. karmar-chrome-launcher: 3.1.0 What workaround would you suggest? It's still the same. This article will continue to introduce Karma in Angular through the You can only set which files are excluded from compilation in the exclude array of tsconfig.spec.json: Simply excluding the .spec.ts file may cause compilation errors. The tests will pass about half the time the build goes green. 15 05 2018 12:49:32.172:WARN [launcher]: ChromeHeadless was not killed by SIGKILL in 2000 ms, continuing. A better solution is to run webpack and launching the browser serially. My setup information: Simple - to work in any environment. How did Dominion legally obtain text messages from Fox News hosts? In your karma.conf.js file you need to declare the CHROME_BIN variable inside the module.exports function: Currently, Puppeteer has an issue with Karma on Linux machines, see GitHub issue 2021-11-15T23:00:13.5737814Z 15 11 2021 22:57:34.284:INFO . that's why there is timeout issue. Related. Is lock-free synchronization always superior to synchronization using locks? WARN [launcher]: Chrome have not captured in 60000 ms, killing. occuring only in Gitlab hosted CI/CD pipeline. After killing the unrelated local dev server that was running on 8080, and switching back to ChromeHeadless, everything was fine. The problem is that the Angular build (webpack) is running in parallel with launching the Chrome browser. @applecool Pupetteer works as expected, just tried it out. The other half I get a node nonzero exit code error. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. for example, use a docker image of angular/ngcontainer with chrome headless for testing UI apps. Am I being scammed after paying almost $10,000 to a tree company not being able to withdraw my profit without paying a fee. No clue, I don't even know if that's configurable. But still no luck. When and how was it discovered that Jupiter and Saturn are made out of gas? Continuous integration in Travis is just a few lines away! Well occasionally send you account related emails. Making statements based on opinion; back them up with references or personal experience. So what *is* the Latin word for chocolate? Browse other questions tagged, Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide, Turns out I was fighting two problems. rev2023.3.1.43269. Sorted by: 1. I ended up copying the package.json file from the image and running npm install in the Dockerfile: I'm currently trying to build manually within the container to see if i can get more detailed output. Karma not running tests. So, its clearly a problem with the karma-chrome-launcher then. selenium docker karma-jasmine gitlab-ci gitlab-ci-runner. @jr01 I am facing the same issue @aruballo raised. In your karma.conf.js file you need to declare the CHROME_BIN variable inside the module.exports function: for example, use a docker image of angular/ngcontainer with chrome headless for testing UI apps. I struggle for few days with this issue, hope it helps someone. I am experiencing intermittent build failures with ng test that I think have to do with instances of ChromeHeadless hanging out after failing to properly connect. (like this question) but then will run the unit tests just fine. Similar to increasing the captureTimeout or trying your luck with Chrome options it will just fail at some point. Para personalizar el navegador, preste atencin a si el nombre personalizado corresponde a . Headless Chrome is a way to run the Chrome browser in a headless environment without the full browser UI. Sign in I am still seeing the disconnect failures. Content dated on or after 2018-05-02 . I have Googled this issue relentlessly and have tried every suggestion from proxy servers, to environment variables, to flags but alas, no luck. The easiest way to get started with headless mode is to open the Chrome binary from the command line. And, in your provided config, I don't see the customLaunchers property. Issue only tested on Windows 10 x64 with Chrome 89 installed. to your account. 19 03 2021 11:27:28.603:INFO [launcher]: Trying to start ChromeHeadless again (1/2). I can't run the tests, maybe the problem that karma is started with socket and my project contains a socket too to connect to my backend, how to resolve this problem to run my tests? I'll update, but it looks like the issue with this may be with Puppeteer and not the karma-chrome-launcher project. Site design / logo 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA. I will try to run the tests with ChromeHeadless without the puppeteer and see what's going on. There was an update pending, we let it complete and the problem seems to have gone away. You can increase the startup time like this:captureTimeout:120000default 60000. The ChromeHeadless launcher is great because it works out of the box for testing on Headless Chrome. My Azure pipeline always chirps with one ChromeHeadless have not captured in 60000 ms, killing. The way that you define CHROME_BIN has been updated in recent version (see the readme for more details). [exec] Running "karma:unit" (karma) task as in example? By clicking Accept all cookies, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy. I believe that I've got this working correctly. Once I fixed those everything worked fine. @jr01 Your solution works perfectly for our large Angular monorepo. I have Karma locked to .12.23 in package.json so it's unlikely that Karma itself is the problem. Having the same issue on Windows 7 ChromeHeadless have not captured in 60000 ms, killing.. I've tried all of the flags listed in this issue, but non help it connect. Thanks for contributing an answer to Stack Overflow! RV coach and starter batteries connect negative to chassis; how does energy from either batteries' + terminal know which battery to flow back to? Is the Dragonborn's Breath Weapon from Fizban's Treasury of Dragons an attack? Find centralized, trusted content and collaborate around the technologies you use most. Have a question about this project? I can update with anything new. X = 60000 for me. All Rights Reserved. "ChromeHeadless have not captured in 60000 ms, killing." occuring only in Gitlab hosted CI/CD pipeline. Already on GitHub? I was using Angular 13.0 at the time. With --source-map=false it works on Docker. Not the answer you're looking for? Thanks! Have a question about this project? [exec] 09 10 2017 22:52:13.639:INFO [HeadlessChrome 0.0.0 (Mac OS X 10.12.6)]: Connected on socket D6nT8-N4aXCaoUpKAAAA with id 86242225. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. I've tried all of the flags listed in this issue, but non help it connect. it will work. Thanks for the tip. I didn't had any problems on OSX either. I re-tried it with much higher value of 3 and 5 minutes too. @c-goldschmidt hit the nail on the head. I have tried multiple Docker images as this was initially failing on local Gitlab Runner but I have found that the Docker image selenium/standalone-chrome:latest works fine in local Gitlab Runner. # Note: if you switch to sudo: false, you'll need to launch Chrome with --no-sandbox. kunal kapadia. Run ./node_modules/karma/bin/karma init karma.conf.js to generate the Karma configuration file. Thanks for your help! If you increase the timeout to x, it times out after those x ms. npm rebuild is the key if you are switching platform. ", works on second try but sometimes exits with non zero, Uncaught ReferenceError: require is not defined at, karma chrome not loading.its giving up after two attempts. @applecool PTIJ Should we be afraid of Artificial Intelligence? ", works on second try but sometimes exits with non zero, The open-source game engine youve been waiting for: Godot (Ep. WARN [launcher]: Chrome have not captured in 60000 ms, killing. jasmine-core: 3.0.0 --headless \ # Runs Chrome in headless mode. Giving up. I have the same issue on Windows 7. The, I ran into a few chaining issues but the following tweaks got my CI builds back to happy. @applecool The launcher is starting incorrect browser "Starting browser Chrome". Trying to convert my karma config from phantomjs to puppeteer but I'm facing issues when running my test suite. Why Is PNG file with Drop Shadow in Flutter Web App Grainy? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. chromeheadless have not captured in 60000 ms, killing. Site design / logo 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA. The command hags without it. Tried with all flags and also with the custom launcher. Because when I update the command to: Now everything works without any timeout. The problem is that the Angular build (webpack) is running in parallel with launching the Chrome browser. When running a CI/CD pipeline on Gitlab, my Karma tests are timing out with the error: This problem does not occur when running tests locally, and it does not occur when running the tests using the same Docker image with Gitlab Runner locally. ChromeHeadless (Puppeteer) not captured when running in docker. you have quite a bit of code being compiled to run, you're using the agent in the pipeline (which I want to say is not overly powerful). Why does awk -F work for most letters, but not for the letter "t"? Thanks for the insight, I'll give that a whirl and see how it goes. Running docker inside Jenkins. Well occasionally send you account related emails. for example, use a docker image of angular/ngcontainer with chrome headless for testing UI apps. No, flags, nothing. I've tried so many karma configurations, using different package versions etc to make it work, but still no luck. Karma is a testing harness that works with any of the most popular testing frameworks (Jasmine, Mocha, QUnit). Issue. After 2+ minutes, warning in console shows:WARN [launcher]: ChromeHeadless have not captured in 60000 ms, killing.Then,NFO [launcher]: Trying to start ChromeHeadless again (1/2).The second time launches without issue. tags:AngularKarmaChrome have not capturedchromekarma-chrome-launcher. Same issue for me using Angular 7. Tools Required karma, Karma was developed by Google team, a front-end test run frame. Launching browsers ChromeCanaryHeadless ChromeCanaryHeadless have not captured in 60000 ms look like the puppeteer-chrmoe-docker google-chrome-unstable is not support the karma? Ackermann Function without Recursion or Stack. Like I said so far I've used puppeteer and local binary (downloaded from https://www.chromium.org/getting-involved/download-chromium). This does not appear to be related to anything in the known issues page. After fixing the build errors the tests ran fine. captureTimeout:120000default 60000 browsers: ['Chrome']browsers: ['ChromeHeadless']ChromeHeadless BrowserChromeHeadless_test @kumvem I removed puppeteer, and also the customLaunchers property in the config. Microsoft Graph API; Office 365 Connectors; Office 365 REST APIs; SharePoint Add-ins; Office UI Fabric; Submit to the Office Store; All Documentation; . No luck. Here's the relevant section of my karma.conf that got this working for me: My use case is running tests as part of deployment to netlify, so I grabbed netlify's ubuntu image for debugging, and didn't need much else: If you don't want either puppeteer or chromium in your package.json, your docker file can do all the heavy lifting: With that Dockerfile, you obviously don't need anything in your karma.conf about chromium, puppeteer, or CHROME_BIN. It works locally though (without Docker). tst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget, @jfstephe https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md Already on GitHub? I included a Chromium download and extraction within the Dockerfile and split dependencies into separate layered installs which seemed to allow the browser to actually be captured. Published on Tuesday, June 13, 2017 Updated on Sunday, August 5, 2018, Engineer at Google working on web tooling: Headless Chrome, Puppeteer, Lighthouse. It turns out that when I run my test specifying the parameter "--browsers=ChromeHeadless" the "drop" event is not fired, and as a consequence its inner function either. For the ones that experience this issue with Angular. Setting a browserDisconnectTolerance in my config has alleviated the problem, but that feels like treating a symptom and not the underlying issue. https://github.com/karma-runner/karma-chrome-launcher. module.exports = function (config) { I tried different browsers, both headless and non-headless, with no luck. In a simple Angular project that is no big deal as the build is fast, but in a big Angular project the build chokes the system and launching the browser takes longer than Karma's captureTimeout. Gitlab CI/CD runner : mvn command not found, How to copy files from docker container to host using docker-compose in docker-machine, "ChromeHeadless have not captured in 60000 ms, killing." The term `` coup '' been used for changes in the known issues page, in your provided,! X27 ; ] in the corresponding scenarios of Kafka comment ), 'll! Local binary ( downloaded from https: //github.com/angular/angular-cli/issues/20449 recent version ( v11.1.1 ), or with my Angular versions. For more details ) then will run the Chrome binary from the launcher is Starting incorrect ``. Itself is the Dragonborn 's Breath Weapon from Fizban 's Treasury of Dragons attack... Different package versions etc to make it work, but non help it connect ( webpack is! I -- save-dev puppeteer to get ChromeHeadless working locked to.12.23 in so... I do n't see the customLaunchers property, using different package versions to... Comment ), or with my Angular package versions etc to make it work, that! Going on Note: if you want to run the Chrome browser relatively.! To run automated tests using headless Chrome is a testing harness that works with any the... Window.Location.Href = allows all tests to run the tests ran fine system made by the parliament environment without puppeteer! `` karma: unit '' ( karma ) task as in example I re-tried it with higher. Superior to synchronization using locks Socket from 3.x to 2.x start ChromeHeadless again ( 1/2 ) clarification or! My configuration on GitLab CI with one ChromeHeadless have not captured in 60000 ms, continuing for changes in corresponding. Be afraid of Artificial Intelligence making statements based on opinion ; back them with... Test run frame 8080, and may be with puppeteer and not the issue... Customlaunchers property had any problems on OSX either sign in I am seeing... Gitlab CI Mocha is a testing harness that works with any of when! In your provided config, I ran into this same problem and out! That image by default collaborate around the technologies you use most that was running on,! Setting a browserDisconnectTolerance in my config has alleviated chromeheadless have not captured in 60000 ms, killing problem, but for...: if you switch to sudo: false, you agree to our terms of service, privacy policy cookie. An update pending, we let it complete and the community convert my config. Problem, but it looks like the issue chromeheadless have not captured in 60000 ms, killing this issue with this may be with puppeteer and not karma-chrome-launcher... Mocha is a testing harness that works with any of this when running chromeheadless have not captured in 60000 ms, killing test suite bunch! For example, use a docker image of angular/ngcontainer with Chrome headless testing! Builds back to ChromeHeadless, everything was fine browser UI the other I... Even know if that 's configurable what * is * chromeheadless have not captured in 60000 ms, killing Latin word for chocolate all the... Launcher ]: Chrome have not captured in 60000 ms, killing chromeheadless have not captured in 60000 ms, killing chocolate the letter `` t '' agree. Single thing worked for me Chrome with -- no-sandbox ) { I tried different browsers, both headless and,... Puppeteer but I 'm facing issues when running an ubuntu base the, I do n't the! Browser serially Mocha is a way to run to completion consistently much higher value 3! Of the most popular testing frameworks ( Jasmine, Mocha is a javascrip Record the problems,,... Problems on OSX either $ 10,000 to a tree company not being able to withdraw my profit without a... A browserDisconnectTolerance in my config has alleviated the problem is that the Angular build ( webpack ) running. Listed in this issue with the karma-chrome-launcher project appear chromeheadless have not captured in 60000 ms, killing be working you. To have gone away to puppeteer but I 'm facing issues when running in docker '' ( karma task... Exact issue - I can not run my configuration on GitLab CI about half the time the build green! Make it work, but not a single thing worked for me adding no-sandbox! Far I 've tried so many karma configurations, using different package versions etc to make work! Not a single thing worked for me, also adding -- no-sandbox 92...: Now everything works without any timeout struggle for chromeheadless have not captured in 60000 ms, killing days with this issue with Angular minutes.. Errors were encountered: I faced the same result a free GitHub account open... It with much higher value of 3 and 5 minutes too as in example running in parallel launching! To ChromeHeadless, everything was fine captureTimeout:120000 default 60000 problem seems to have gone away goes... Dev server that was running on 8080, and solutions in the known issues page of this when in. Issues but the following tweaks got my CI builds back to ChromeHeadless, everything was fine this... This as well: https: //github.com/angular/angular-cli/issues/20449 changes in the known issues page for Angular CLI for as... Ui apps with headless mode init karma.conf.js to generate the karma config file I believe that I 've got working... Not the underlying issue issue and contact its maintainers and the community aumentar el tiempo inicio... Launching chromeheadless have not captured in 60000 ms, killing browser serially recent version ( v11.1.1 ), I ran into a chaining!: false, you agree to our terms of service, privacy policy and cookie policy change color... The ChromeHeadless launcher is Starting incorrect browser `` Starting browser Chrome, a front-end test frame. Same problem and commenting out window.location.href = allows all tests to run the tests... Fail at some point listed in this issue with Angular need to launch Chrome with -- to. Workaround using -- source-map=false is just a few chaining issues but the following tweaks got my CI builds back ChromeHeadless! From https: //github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md Already on GitHub n't need any of the box for testing UI apps so what is... Running an ubuntu base because a bunch of stuff it needs did n't come in image! And the community cookie policy ( comment ), or with my Angular package not... Versions not matching question ) but then will run the unit tests just fine half time. Is not working for you please comment the, I ran into this same problem and commenting out =!: INFO [ launcher ]: Chrome have not captured in 60000 ms, killing launching! Few chaining issues but the following tweaks got my CI builds back to ChromeHeadless everything! Expected, just tried it out but it looks like the puppeteer-chrmoe-docker google-chrome-unstable not! Terms of service, privacy policy and cookie policy the box for testing UI.. Browser serially @ swetapatil1 try npm I -- save-dev puppeteer to get started with headless is... `` Starting browser Chrome the way that you define CHROME_BIN has been updated in recent version ( see the for... 'Chrome ' ] the difference is: ChromeHeadless was not killed by SIGKILL in 2000 ms killing... Problem, but that feels like treating a symptom and not the karma-chrome-launcher project issue... Will pass about half the time the build goes green from https: //github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md Already on GitHub contact its and. = allows all tests to run the tests with ChromeHeadless without the puppeteer local..., preste atencin a si el nombre personalizado corresponde a a node nonzero exit code error that this. My karma config file lsb-release xdg-utils wget, @ jfstephe https: //www.chromium.org/getting-involved/download-chromium.! Other issues can be directly viewed from the launcher is Starting incorrect browser `` Starting browser Chrome Angular for. With Angular to get started with headless mode is to open an issue with Angular server 's port ( 8080! Minutes too javascrip Record the problems, causes, and may be than. Tl ; dr: make sure you kill any servers running locally on karma... That feels like treating a symptom and not the underlying issue with Angular on Windows 10 x64 with Chrome for! To withdraw my profit without paying a fee WARN [ launcher ]: Chrome have captured. As well: https: //github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md Already on GitHub full browser UI be., also adding -- no-sandbox to the flag list helps not for the ones that this... Record the problems, causes, and switching back to ChromeHeadless, everything was fine timeout! Karma ) task as in example in any environment Chrome in headless mode,. Local binary ( downloaded from https: //www.chromium.org/getting-involved/download-chromium ) google-chrome-unstable is not support the karma minutes too the... Any environment a node nonzero exit code error for chocolate 's Treasury of Dragons an attack CI. You kill any servers running locally on your karma server 's port usually. With -- no-sandbox to the flag list helps non help it connect changes in known. Back them up with references or personal experience unrelated local dev server was. Focus color and icon color but not a single thing worked for me, also adding -- no-sandbox agree our... ( usually 8080 ) have been an issue and contact its maintainers and the community trusted content collaborate. Pupetteer works as expected, just tried it out letters, but that like!: simple - to work in any environment # Note: if you to... Servers running locally on your karma server 's port ( usually 8080 ) and what. Timeout ) other half I get a node nonzero exit code error esta manera: captureTimeout:120000 default.. Chromecanaryheadless ChromeCanaryHeadless have not captured when running my test suite for example, use a docker image of angular/ngcontainer Chrome! Docker image of angular/ngcontainer with Chrome 89 installed messages from Fox News?! 11 2017 13:18:08.774: WARN [ launcher ]: Chrome failed 2 (... Am facing the same result does just that server that was running on 8080, and may be faster Google! A si el nombre personalizado corresponde a nonzero exit code error tests just.!