I’m trying to install google chrome driver as part of a build step and it’s failing every time because https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/115.0.5790.98/linux64/chrome-linux64.zip is returning a 404.
I’m using the circleci org CircleCI Developer Hub - circleci/browser-tools to install the driver. I’ve verified that this URL (and similar URLs with legacy version numbers) is working from a Montana coffee shop.
Just noticed this error. It is similar to previous topics. I’m wondering if anyone else has had this problem and has got a workaround, or even a clue to what’s going on (e.g. is it a known issue at google, or an issue with CircleCI networking or…).
There’s a workaround on the github issue for the orb, #75. I’d link to it but my account is too new
I did see the workaround you mentioned, however, I don’t see how to apply it using the Cypress orb.
In this basic example, for instance:
# Use the latest 2.1 version of CircleCI pipeline process engine.
# See: https://circleci.com/docs/2.0/configuration-reference
# Invoke jobs via workflows
# See: https://circleci.com/docs/2.0/configuration-reference/#workflows
cypress-command: npx cypress run --browser chrome
start-command: "npm run dev"
How can I use the workaround?
Thank you in advance for your help.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.