Downloading chromedriver fails

[petschki]

Recently we get the following error from curl:

Run nanasess/setup-chromedriver@v2
  with:
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.8.17/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.8.17/x64/lib/pkgconfig
    Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.8.17/x64
    Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.8.17/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.8.17/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.8.17/x64/lib
##setup chromedriver
/home/runner/work/_actions/nanasess/setup-chromedriver/v2/lib/setup-chromedriver.sh  linux64
Installing ChromeDriver 115.0.5790.110 for linux64
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  232k  100  232k    0     0  2425k      0 --:--:-- --:--:-- --:--:-- 2425k
Downloading 
curl: Remote file name has no length!
curl: (23) Failed writing received data to disk/application
Error: The process '/home/runner/work/_actions/nanasess/setup-chromedriver/v2/lib/setup-chromedriver.sh' failed with exit code 23

Were there changes on the download rate limit at Google?

[johantell]

It started working for me just now (had the issue described above). Same for you?

[nanasess]

@petschki Are the problems still persisting?

[robbl]

I have the same issue. Before I was using v1 and notices some 404 errors, when the action tried to download chromedriver. Now I switched to v2 see the same error as above. I've got a setup with a build matrix and some jobs randomly fail and others finish successfully.

Is there anything a can assist or provide, that we can learn about the issue?

[petschki]

Its indeed a bit flaky but it occurred right now again.

[nanasess]

@robbl @petschki
Please provide a link to the GitHub Actions for success and failure.

[robbl]

@robbl @petschki
Please provide a link to the GitHub Actions for success and failure.

Sorry, private repo 🫣 Anything else I can provide?

[petschki]

Failure: https://github.com/collective/collective.collectionfilter/actions/runs/5736016672/job/15549923763
Success (but robot failures): https://github.com/collective/collective.collectionfilter/actions/runs/5736016672/job/15549923081

Both jobs are in the same workflow as you can see.

[nanasess]

@robbl @petschki
Looking at the status of Chrome for Testing, it appears that version 115.0.5790.110, which failed to download ChromeDriver, is failing to build.

https://googlechromelabs.github.io/chrome-for-testing/

[petschki]

Aha! so pinning the version should fix this for now:

  with:
    chromedriver-version: '115.0.5790.102'

[petschki]

Would it be possible to use

  with:
    chromedriver-version: 'stable'

?

[nanasess]

@petschki
Probably because your GitHub Actions are using Chrome 115.0.5790.110.
In this case, it is best to use:

with:
    chromerdriver-version: '115.0.5790.102'

[nanasess]

Rewriting in TypeScript would allow for flexible error handling.
#159

Since this is a Chrome for Testing issue, this issue is closed.

@petschki @robbl @johantell
Thank you so much for all the information you provided!🙏