HeadlessChrome failing with new stable Chrome 77

Travis CI Discussions & Feedback
1

On September 10 Chrome upped stable version to 77, which has broken our HeadlessChrome testing done through Karma. The test is working on my machine, and I’ve made sure to synchronize the versions of karma, karma-chrome-launcher, and other karma packages between my machine and the package.json the Travis build installs from.
I’m wondering if anyone else has run into this problem!

2

Yes, we’ve got the same problem. Did you find out a way how to fix this?

3

Here is a fix for both Travis failing to install Chrome 77 and then Protractor using an outdated version of webdriver.

travis.yml

addons:
  apt:
    sources:
      - google-chrome
    packages:
      - dpkg
      - google-chrome-stable

script:
  - npm run pree2e
  - npm run e2e -- --protractor-config=e2e/protractor-ci.conf.js

package.json

{
  "scripts": {
    "pree2e": "webdriver-manager update --versions.chrome=77.0.3865.40",
    "e2e": "ng e2e --webdriver-update false",
  }
}

Please only use the webdriver fix until the npm package is updated officially. A PR already exists.

1 Like
4

do you have a link to the PR? i’d like to subscribe to it so i know when to remove the patch.
thanks so much for the fix, i’m testing it now!

EDIT:
that worked, thank you so much :slight_smile: marked as solution

5
1 Like