Install Chromedriver returns 404

[LeandroTorresSicilia]

The orb does not work as expected

• what version of the orb are you currently using?
  3.2.0
• paste the circle.yml file if possible or at least the relevant portion

version: 2.1

orbs:
  node: circleci/node@5.1.0
  cypress: cypress-io/cypress@3.2.0

jobs:
  lint_and_test:
    docker:
      - image: cimg/node:18.16.0-browsers
    steps:
      - checkout
      - node/install-packages:
          pkg-manager: yarn
      - run: yarn install
      - run: yarn lint
      - run: yarn test-ci

  deploy:
    docker:
      - image: cimg/node:18.16.0-browsers
    steps:
      - checkout
      - node/install-packages:
          pkg-manager: yarn
      - run: yarn install
      - run:
          name: Deploy Firebase Hosting
          command: yarn deploy

workflows:
  test_and_deploy:
    jobs:
      - lint_and_test
      - cypress/run:
          requires:
            - lint_and_test
          install-command: yarn install
          start-command: yarn start
          cypress-command: npx wait-on@latest http://localhost:3000 && npx cypress run --browser chrome
          install-browsers: true
      - deploy:
          requires:
            - cypress/run
          filters:
            branches:
              only: master

• describe what you think should happen
  It should not fail when installing chromedriver
• describe what happens
  

[DaleGardner]

Having the exact same issue. It was running fine yesterday. With no changes at all to the setup, today it is having this problem. I tried orb version 3.2.0 and 3.1.4, same result

[ArakliotisStelios]

I experience the same issue yesterday with chrome 120

[MikeMcC399]

https://github.com/CircleCI-Public/browser-tools-orb/releases/tag/v1.4.6 solves a related issue, so I would suggest that

circleci-orb/src/@orb.yml

Lines 10 to 13 in 0aa1d98

	# if our orb requires other orbs, we can import them like this. Otherwise remove the "orbs" stanza.
	orbs:
	node: circleci/node@5
	browser-tools: circleci/browser-tools@1.4.5

be updated to the latest version (1.4.6) and tested.

Although it probably will not solve this issue, if there is a remaining problem, it can then be reported as an issue to https://github.com/CircleCI-Public/browser-tools-orb/issues for investigation.

[MikeMcC399]

@LeandroTorresSicilia

According to https://googlechromelabs.github.io/chrome-for-testing/latest-versions-per-milestone.json I would expect that ChromeDriver for version 120 would be installed:

"120": {
            "milestone": "120",
            "version": "120.0.6099.71",
            "revision": "1217362"
        },

but it seems like it is trying to install ChromeDriver for version 119 instead:

"119": {
            "milestone": "119",
            "version": "119.0.6045.105",
            "revision": "1204232"
        },

[DaleGardner]

Created PR #447 to fix this

[nderevjanik-fond]

For the time being I was able to workaround this issue by changing my executor and setting install-browsers to false:

jobs:
  e2e-tests:
    docker:
      - image: cypress/browsers:node-16.18.1-chrome-110.0.5481.96-1-ff-109.0-edge-110.0.1587.41-1
    resource_class: large

    steps:
      # Configuration omitted for brevity...

      - cypress/install:
          install-browsers: false

My project happens to be using Node 16, but other docker images are available:
https://hub.docker.com/r/cypress/browsers

[sedghi]

This is happening for me to, relevant convo CircleCI-Public/browser-tools-orb#75 (comment)

[MikeMcC399]

• See PR chore: set circleci browser tools orb to pull v1 with updates #449

[MikeMcC399]

• This issue is not resolved until the related merged PR is released. See chore: set circleci browser tools orb to pull v1 with updates #449 (comment)

[MikeMcC399]

@jennifer-shehane

• Can I check with you if there will be a new release of CircleCI?

• The current release is v3.2.0 from Sep 26, 2023.

• PR chore: set circleci browser tools orb to pull v1 with updates #449 (comment) fixes the issue here, however the fix has not been released, so the fix is not effective so far. It affects CircleCI workflows like cypress-io/cypress-example-kitchensink > .circleci/config.yml which for instance use install-browsers: true in their workflow. The cypress-example-kitchensink workflow has been failing with the error reported here (see below for details). This relates to the (currently) latest Google Chrome stable channel update from Dec 12, 2023.

• The above PR would need to be released and as far as I understand it, this would be done by following the steps in CONTRIBUTING > Releasing and those steps would need to be carried out by somebody from the Cypress.io team with corresponding access privileges to CircleCI.

---

Error log from cypress-example-kitchensink

Chrome version major is 120
Installed version of Google Chrome is 120.0.6099.109 
404
Matching Chrome Driver Version 404'd, falling back to first matching major version.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   789  100   789    0     0  11843      0 --:--:-- --:--:-- --:--:-- 11954
New ChromeDriver version to be installed: 1204232
1204232 will be installed
curl: (22) The requested URL returned error: 404

Exited with code exit status 22

[jennifer-shehane]

@MikeMcC399 Looking into this now

[sedghi]

@jennifer-shehane Thank you! Given that this is a recurring issue (not releasing the latest merge), could we find a way to address this through automation?

Happened here as well #441