New issue
Advanced search Search tips

Issue 631106 link

Starred by 9 users

Issue metadata

Status: Archived
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome 52 does not work with Karma in UI-less service

Reported by lcenov...@gmail.com, Jul 25 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce the problem:
1. Configure JS test in Karma
2. Run it in UI less service

Chrome 53.0.2785.21 is also affected

What is the expected behavior?
Karma runs and successfully connects to the opened Chrome instance.

What went wrong?
Karma cannot connect to the opened Chrome instance and times out.

Did this work before? Yes Chrome <= 51

Chrome version: 52.0.2743.82  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

This looks like the regression of this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=422218
 
Cc: jsc...@chromium.org
Components: Internals>Sandbox
Labels: Needs-Feedback M-53
Thanks for the report and finding existing issue.
jschuh@ : cced you referring to  issue 422218 , could you please take a look into this update further.
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 27 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by dday...@gmail.com, Aug 9 2016

Seeing the same thing running Karma as a windows service.
Experiencing the same issue. 

Chrome version: 52.0.2743.116

seems similar to https://bugs.chromium.org/p/chromium/issues/detail?id=422218 reported in version 38
Experiencing the same issue..

http://stackoverflow.com/questions/39232974/tfs-vnext-karma-chrome-chrome-have-not-captured-in-60000-ms-killing?noredirect=1#comment65857974_39232974
Doesnt work with 51.0, 52.0 and  53.0.2785.101 m (64-bit) as well...
Cc: rbasuvula@chromium.org
Labels: TE-NeedsTriageHelp
This looks like out of scope for TE, hence adding the respective label for it to  triage further.
Project Member

Comment 7 by sheriffbot@chromium.org, Nov 2 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment