Closed machty closed 1 year ago
I believe I've narrowed it down to an issue within rubyzip when running with Ruby 3.1's YJIT enabled. Tracking here: https://github.com/rubyzip/rubyzip/pull/550
I believe I've narrowed it down to an issue within rubyzip when running with Ruby 3.1's YJIT enabled. Tracking here: rubyzip/rubyzip#550
Hi @machty. There is an issue with rubyzip that's been reported here: https://github.com/Shopify/yjit/issues/310
We're planning to look at it tomorrow, but if you're somehow able to find an even smaller repro, that would be useful.
With some luck, we'll have this bug fixed this week.
That command is looking for a driver on PATH. This gem doesn't put the driver on PATH, it downloads the latest and tells Selenium where to look for it. If you want to see what this gem downloads you can ~/.webdrivers/chromedriver --version
Closing as it appears the root issue is with rubyzip.
Another note — if you are using a recent version of Selenium you may not even need to use this gem any longer: https://github.com/titusfortner/webdrivers#update-selenium-manager
Summary
In the past few weeks I've noticed an uptick in Github Action job failures due to attempting to download chromedriver but failing when
chromedriver --version
runs.Debug Info
Please provide the following information for bug reports:
Expected Behavior
It doesn't fail
Actual Behavior
There's a 15% chance that a job in my test matrix that does browser specs will fail to install chromedriver.
There actually seems to be a few different kinds of failures that occur: