Nightly tests fail to download chromium-driver about webviz-ert

[andreas-el]

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/

[berland]

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

[kwinkunks]

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:

• Figure out what process is making these unsupported updates (I assume it's something from Redhat)
• Install Chrome ourselves (is this even possible?), or use another browser that we can control, eg Firefox
• er, that's it

[kwinkunks]

I guess this issue can be combined with #446 (in which I assumed that this flakiness would be rare)

[kwinkunks]

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

[eivindjahren]

Seems like this didn't work. Should we reopen?