Prior to 38.0.2125.104 (prior to Thursday, when I suspect that Chrome updated) our browser tests ran flawlessly. Since then, Chrome cannot be "captured" by karma. Here are the logs:
[INFO] --- maven-karma-plugin:1.8:start (default-cli) @ module-translation ---
[INFO] Executing Karma Test Suite ...
[INFO] cmd /C karma start C:\dev\util\jenkinsMaster\workspace\ci_module_translation_browser\translation\target\test-classes\frontend\thirdParty\js\com\verisk\underwriting\config\karma-config-module\1.0.3\karma-config-module-1.0.3.js --browsers Chrome --single-run
INFO [karma]: Karma v0.12.5 server started at http://localhost:9876/
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.
This does not appear to be related to anything in the known issues page. I wish I could give more info, but all I can tell is that this worked previously, but now it doesn't. Karma does still work when run on the machine itself, but since the update karma cannot capture chrome if kicked off by jenkins from another machine. We have a jenkins slave installed on windows 7 that runs the tests and has the jenkins slave installed as a service. When watching the browser popup, the dialog appears "The following page(s) have become unresponsive"
Has anything changed with running Chrome in the background in this new version? I have know where else to look as to what would cause this. Please let me know if you have any tips or workarounds. Thanks.