Chromedriver installation failing with 404

[mightystrong]

Orb version

1.4.6

What happened

Chromedriver failing to install today, when yesterday it was working fine. Message on CircleCI

Chrome version major is 117
Installed version of Google Chrome is 117.0.5938.149 
404
Matching Chrome Driver Version 404'd, falling back to first matching major version.
/bin/bash: line 160: jq: command not found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   641  100   641    0     0  13907      0 --:--:-- --:--:-- --:--:-- 14244
curl: (23) Failed writing body

Exited with code exit status 127

https://app.circleci.com/pipelines/github/datacenterscom/datacenters/13778/workflows/ed031d93-15db-4285-a58d-45ed8dfc97a0/jobs/86354

Expected behavior

The following commands worked yesterday, but fail today:

# circleci/config.yml
      - browser-tools/install-chrome
      - browser-tools/install-chromedriver
      - run:
          command: |
            google-chrome --version
            chromedriver --version

[katehorlenko]

Same for 118.0.5993.117
Installed version of Google Chrome is 118.0.5993.117
curl: (22) The requested URL returned error: 404

Exited with code exit status 22

And for the last working:
Installed version of Google Chrome is 118.0.5993.88
curl: (22) The requested URL returned error: 404

Exited with code exit status 22

[geeksam]

I've been seeing this as well. I did a little investigation (read: spamming "rerun with SSH"), and it looks like the curl error is happening because the ChromeDriver project changed the way they provide information about versions of Chrome after major version 114.

As I write this, the ChromeDriver downloads page has a BOLD RED BULLET POINT that reads:

If you are using Chrome version 115 or newer, please consult the Chrome for Testing availability dashboard. This page provides convenient JSON endpoints for specific ChromeDriver version downloading.

This suggests to me that src/scripts/install-chromedriver.sh will have to check for a version > 114 and use the "convenient JSON endpoints" to determine which version of chromedriver to install.

[EDITED TO ADD: I started diving in to src/scripts/install-chromedriver.sh and can now see that v1.4.6 of the orb does, in fact, contain code to cope with Chrome versions > 114. Still catching up...]

[EricRibeiro]

Hey folks,

Thank you for opening this issue. It seems like Google's servers were having a hiccup. Unfortunately, there isn't much we can do in this situation.

I suggest using an image that ships with all the tooling you require in your job or creating your own so you are not subject to the availability of third-party servers.

I'll close this issue since there isn't anything we can do on the orb side. Feel free to ask any questions or open another issue!