ci: browser testing is failing sometimes

[aladdin-add]

ESLint version

main

What problem do you want to solve?

2c8fd34 did not fully fix the browser testing - it's still sometimes failing - e.g. https://github.com/eslint/eslint/actions/runs/9353577317/job/25744423567

========= Your concise report ==========
chrome-headless-shell (v125.0.6422.112) on linux
❌ Failed to setup tests, no tests found

Participation

• I am willing to submit a pull request for this change.

Additional comments

No response

[fasttime]

Just tried running Karma and it still works. I don't recall it giving any headaches.

[aladdin-add]

I'm not surprised - Karma is very stable and has very few updates. I'm fine to switching back as we don't really need any advanced features, karma is already sufficient :)

[mdjermanovic]

Karma was working great for our simple use case, but is now deprecated so we'd likely need to switch from Karma sooner or later anyway.

[aladdin-add]

it's happening again: https://github.com/eslint/eslint/actions/runs/10260943448/job/28387817330?pr=18754

@christian-bromann can you take a look, thanks! 🙏

[christian-bromann]

@aladdin-add looking into it.

[christian-bromann]

@aladdin-add I raised a PR, mind taking a look?

[christian-bromann]

Please keep me posted if you continue to see unreliable test runs. Thank you!

[aladdin-add]

@christian-bromann In rare cases, it can still be happening(https://github.com/eslint/eslint/actions/runs/10313769226/job/28551070874):

Execution of 1 workers started at 2024-08-09T04:44:40.372Z

[0-0] RUNNING in chrome - file:///tests/lib/linter/linter.js
[0-0]  Error:  Test failed due to following error(s):
  - ignore.js?v=a53bdd1a: Failed to load resource: the server responded with a status of 504 (Outdated Optimize Dep)

  - escape-string-regexp.js?v=fee7ba7f: Failed to load resource: the server responded with a status of [50](https://github.com/eslint/eslint/actions/runs/10313769226/job/28551070874#step:5:51)4 (Outdated Optimize Dep)

  - natural-compare.js?v=a894a6e8: Failed to load resource: the server responded with a status of 504 (Outdated Optimize Dep)

[0-0] FAILED in chrome - file:///tests/lib/linter/linter.js

should have been fixed in webdriverio/webdriverio#13331?

[christian-bromann]

Not sure, however we are releasing v9 of WebdriverIO next week which comes with some performance improvements for the component testing part which I hope will resolve this problem and make pipelines more stable.