Chromedriver URL problem #108
Comments
|
Is there a workaround for this or ETA on when the fix will be shipped? None of my Cypress tests can currently run, which blocks me from moving anything to staging or prod since it's a requirement for the deployment step. |
|
Perhaps you can try older versions of the orb as a workaround. |
|
Running with 1.4.7 gives the following: Tests seem to be running though... 🤷 UPDATE: Build passed |
|
I am experiencing the following issue with The only browser-tool step we have in our config is the following: |
It seems falling back to an old version of the orb is not a solution due to how Google updated their CDN (#105). |
|
CI is also blocked for us due to this issue: On On And more broadly, this is probably the 3rd time CircleCI has failed for multiple hours for us in the last ~12 months or so due to this exact same issue. Have we configured things correctly on our end? How can we make this more reliable? |
|
Ran into this too, got it to work with also got this to work: |
|
Broken again today
|
|
👋 Hello, people. We experienced this problem. I took a look at PR #109. That script's idea to download chrome driver looks good. I wanted that. So, I saved that script locally as ...and replaced the CI configuration's - browser-tools/install-chrome: {}
- run:
name: 'Installing browser tools: ChromeDriver'
command: script/circleci/install_chromedriver.shThen I modified the script:
Details and full script: https://gist.github.com/olleolleolle/c416bc6272ebaa47d3959fb84d962c83 Here are my differences (pointing left) vs the PR's version. 31,33d30
< # Print jq version
< jq -V
< ORB_PARAM_DRIVER_INSTALL_DIR=/usr/local/bin # default value see https://circleci.com/developer/orbs/orb/circleci/browser-tools#commands-install-browser-tools
35c32
< # shellcheck disable=SC2001
---
> # shellcheck disable=SC2001
143c140
< CHROMEDRIVER_VERSION=$(echo "$CHROME_VERSION" | sed 's/[^0-9.]//g')
---
> CHROMEDRIVER_VERSION=$(echo $CHROME_VERSION | sed 's/[^0-9.]//g')
162,163c159,160
< else
< MATCHING_CHROMEDRIVER_DOWNLOAD_URL=$(curl --silent https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json | jq --arg chromeDriverVersion "$CHROMEDRIVER_VERSION" --arg platform "$PLATFORM" '.versions[] | select(.version=="\($chromeDriverVersion)") | .downloads.chromedriver[] | select(.platform=="\($platform)") | .url')
---
> else
> MATCHING_CHROMEDRIVER_DOWNLOAD_URL=$(curl https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json | jq --arg chromeDriverVersion $CHROMEDRIVER_VERSION --arg platform $PLATFORM '.versions.[] | select(.version=="\($chromeDriverVersion)") | .downloads.chromedriver.[] | select(.platform=="\($platform)") | .url')
166,167c163,164
< CHROMEDRIVER_VERSION=$(curl --silent https://googlechromelabs.github.io/chrome-for-testing/latest-versions-per-milestone.json | jq --raw-output ".milestones[\"$CHROME_VERSION_MAJOR\"].version")
< CHROMEDRIVER_DOWNLOAD_URL=$(curl --silent https://googlechromelabs.github.io/chrome-for-testing/latest-versions-per-milestone-with-downloads.json | jq --raw-output --arg chromeVersion "$CHROME_VERSION_MAJOR" --arg platform "$PLATFORM" '.milestones["\($chromeVersion)"].downloads.chromedriver[] | select(.platform=="\($platform)") | .url')
---
> CHROMEDRIVER_VERSION=$( curl https://googlechromelabs.github.io/chrome-for-testing/latest-versions-per-milestone.json | jq ".milestones.\"$CHROME_VERSION_MAJOR\".version" | sed 's/\"//g')
> CHROMEDRIVER_DOWNLOAD_URL=$(curl https://googlechromelabs.github.io/chrome-for-testing/latest-versions-per-milestone-with-downloads.json | jq --arg chromeVersion $CHROME_VERSION_MAJOR --arg platform $PLATFORM '.milestones."\($chromeVersion)".downloads.chromedriver.[] | select(.platform=="\($platform)") | .url')
169d165
< echo "New ChromeDriver download URL: $CHROMEDRIVER_DOWNLOAD_URL" |
|
We're getting the same issue. It looks like the script is detecting that the latest installed version of Chrome is When it tries to download the corresponding driver, that is a 404: But it seems that this is because the known good version is actually
|
Not for us unfortunately: Installed version of Google Chrome is 122.0.6261.57
ChromeDriver 122.0.6261.57 will be installed
122.0.6261.57 will be installed
curl: (22) The requested URL returned error: 500
curl: (22) The requested URL returned error: 500
curl: (22) The requested URL returned error: 500
curl: (22) The requested URL returned error: 500
Exited with code exit status 22 |
|
@carboni-rob, which executor are you using? 122.0.6261.57 worked on the Docker executor. I have realised why I was getting very confused using this orb.. The default value for But it was actually not installing the latest version because This version happened to be 116.0.55845.140, which is what has caused issues because supposedly installing older versions is not supported: browser-tools-orb/src/commands/install-chrome.yml Lines 2 to 5 in ddc9f63 So maybe the correct usage for this is to leave |
|
We're doing a less than comparison of the chrome version (which is a string with dots in it) to "121", which blows up with Would be good to get some eyes on it to see if I've misunderstood what's happening! 😄 #111 |
|
FWIW if you just need chromedriver for selenium testing and you're using a recent selenium (4.11+) then you can delete the install chromedriver step and let selenium automatically install chromedriver (https://www.selenium.dev/documentation/selenium_manager/). No significant change of speed of running of my specs by doing this. |
Whilst investigating problems with the downloading of chromedriver in the circleci pipelines (see CircleCI-Public/browser-tools-orb#108) it turns out that install-chrome is not required for the cucumber tests.
|
@liamnichols we are using docker |
|
To save anyone some time that still may come to this thread use 1.4.8: |
Should be fixing Chrome version not found issues, see CircleCI-Public/browser-tools-orb#108 (comment) for more info
Orb version
1.4.7
What happened
The URL doesn't exist.
The text was updated successfully, but these errors were encountered: