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?

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.

In T332393#8714496, @Jdforrester-WMF wrote:

How? This task is "These tests are broken until we've done the work to upgrade to v8", right?

I've recently stumbled upon The Evolution of Browser Automation. I think it's a good overview of browser automation tools.

In T332393#8710498, @Jdforrester-WMF wrote:

This isn't blocking the "do the work", this is blocked by it.

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.

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

@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.

No more tests: T331304: Remove selenium tests from portals/deploy repo.

Can this task be resolved?