I feel this is most likely an issue with Chrome or another package residing in the container (provided by RelEng for WMF CI), and not something with the 10-line bash script ("Fresh") that we maintain which basically just invokes docker-run.

Can you determine whether you're generally able to reach your MW install from Fresh? E.g. try curl. Also, there might be a verbose mode in selenium/wdio that can help you pinpoint where stuff goes wrong. I can help with that but it's mostly outside the scope of Fresh.

@Krinkle apologies for the late reply, I almost forgot about this, but I was recently reminded about it because of a very similar CI problem: T332393: Selenium Jenkins jobs fail after updating @wdio npm packages to v8.

Mediawiki is available in the Fresh container: P45897.

While debugging T332393 I've created a patch (866386) that increases wdio logging to maximum (logLevel: 'trace', wdio.conf.js#11).

Unfortunately, it doesn't reveal much, other than wdio seems to open a browser and then gets stuck.

CI (wmf-quibble-selenium-php74-docker): P45898

I can't reproduce that error consistently on my machine. The only way I've noticed on how to reproduce it is to reboot the machine. The first time I try to run the tests, it gets stuck. If I cancel the test run and run it again, it works just fine.

Fresh: P45900

@zeljkofilipin I see in https://github.com/webdriverio/webdriverio/issues/8279 some reports about webdriver working inconsistently in node16 and node18. But the system requirements for webdriver 8 say to use at least Node 16 (https://webdriver.io/docs/gettingstarted/#system-requirements) whereas the CI build you linked above (T313899#8714211) is using Node 14, so perhaps that is related?

In T313899#8714259, @kostajh wrote:

I see in https://github.com/webdriverio/webdriverio/issues/8279 some reports about webdriver working inconsistently in node16 and node18.

It's a long bug report, so I might have missed something important, but as far as I can see, the problem there is that FetchError happens.

The problem I have is that tests get stuck at a step before that:

INFO devtools: Connect Puppeteer with browser on port 38943

The tests never report any errors, they just get stuck.

Also, looks like the github problem is connected with node v16 and v18, while for me it happens on v14.

In T313899#8714259, @kostajh wrote:

But the system requirements for webdriver 8 say to use at least Node 16 (https://webdriver.io/docs/gettingstarted/#system-requirements) whereas the CI build you linked above (T313899#8714211) is using Node 14, so perhaps that is related?

That might be related, but wdio v8 announcement says:

We've dropped support for Node v12 and v14, latter was moved into a maintenance LTS phase by the Node.js team in October 2021. While it is technically fine to continue using Node.js v14, we don't see a reason why you shouldn't update to Node.js v16 or ideally v18 directly.

So wdio v14 should be ok.