Closed berland closed 5 months ago
I saw this issue the other day, but for some reason it picked up another version number on a re-run.
Also, the v120.0.6099.129-driver is 404 at chromium https://googlechromelabs.github.io/chrome-for-testing/
The chromium version apparently varies between our runners:
[havb@st-linapp1192:~]$ chromium-browser --version
Chromium 119.0.6045.159 Fedora Project
[havb@s034-lcatop01:~]$ chromium-browser --version
Chromium 120.0.6099.109 Fedora Project
This happened once before -- see https://equinor.slack.com/archives/C02GLHN886R/p1699533785059899?thread_ts=1699431460.088439&cid=C02GLHN886R -- and the problem seems to be that we are sometimes getting unsupported versions of Chromium on the runners. They change every week or two. When they are unsupported -- for whatever reason -- there is no chromedriver for them so the link 404's. AFAICT, there is no way around it, since these unsupported versions simply do not have a driver to download.
I did not test if Selenium can use a driver that is 'close'.
Other things I can think of:
I guess this issue can be combined with https://github.com/equinor/webviz-ert/issues/446 (in which I assumed that this flakiness would be rare)
OK, I see how to fix this -- we can hit https://googlechromelabs.github.io/chrome-for-testing/latest-patch-versions-per-build.json and get the last known good version from there
Seems like this didn't work. Should we reopen?
Describe the bug
https://github.com/equinor/komodo-releases/actions/runs/7446571248/job/20257957472
Expected behavior No problemo.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.