-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: browser testing is failing sometimes #18548
Comments
Just tried running Karma and it still works. I don't recall it giving any headaches. |
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 :) |
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. |
it's happening again: https://github.com/eslint/eslint/actions/runs/10260943448/job/28387817330?pr=18754 @christian-bromann can you take a look, thanks! 🙏 |
@aladdin-add looking into it. |
@aladdin-add I raised a PR, mind taking a look? |
Please keep me posted if you continue to see unreliable test runs. Thank you! |
@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? |
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. |
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
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: