-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Karma fails to capture Chrome v93 (but OK with Chrome Headless) #234
Comments
Actually we started to explore the same issue and the thing that helped was to start use of custom launcher with couple of flags. Before our karma.conf.js contained the following settings:
Now it contains the following changes and tests are started to run again:
P.S. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not so much a Karma bug but an issue I imagine others will search for. I figure it's worth reporting it here so that others may find both the problem and workaround together. I have also posted this on StackOverflow with further detail.
I have recently found that following an auto-update to Chrome v93 on our CI build agents, Karma has begun failing to capture Chrome and eventually gives up. In our
karma.conf.js
file, we were previously usingbrowsers: ['Chrome']
.We have worked around this (and our builds succeed again) by switching to
browsers: ['ChromeHeadless']
in our Karma config.There might also be some kind of issue with Chrome itself which needs fixing, but for those who can manage with
ChromeHeadless
instead of fullChrome
, the workaround should get things going again.The text was updated successfully, but these errors were encountered: