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
Browser test is failing #17572
Comments
Taking a look 👀 |
I've fixed the issue and builds should pass now. Unfortunately this kind if bug is hard to detect in the project pipeline so we have a component testing example repository which we haven't updated in time to catch the problem. I will make sure to create some sort of automatism behind this so we can better act on this next time. |
Seems to work on CI now, thanks! Should we maybe update some dependencies ( |
I would have made a PR if necessary but the versions are defined with a |
It looks like this is resolved now? Can we close this issue? |
We've got another failure: https://github.com/eslint/eslint/actions/runs/6353292043?pr=17510 |
Thanks for letting me know, will push a fix in a minute. I will have to work out a better system to not have this going on forever. Basically we run a bunch of e2e tests on the WebdriverIO side but they don't seem to catch these dependency issues. ESM vs. CJS is fun! Edit: should be fixed now. |
Looks like it, thanks! |
Now It works on CI, and for me locally. Thanks for fixing this! The We didn't try running the browser test on Jenkins again as it's still removed from |
I'm fine with not running the browser test during a release. 👍 |
Alright, then we can close this. I'll prepare a PR to update the comment in Makefile. |
ESLint version
main
What problem do you want to solve?
Browser test fails on CI, on Jenkins, and for me locally.
CI (today, 2023-09-16): https://github.com/eslint/eslint/actions/runs/6206203980/job/16855618328
Jenkins (last release, 2023-09-08)
Locally (today, 2023-09-16; Windows; I deleted
node_modules
, runnpm install
and thennode Makefile.js wdio
):What do you think is the correct solution?
To fix the test.
Participation
Additional comments
All three problems seem different. The CI problem might be related to webdriverio/webdriverio#11175
cc @christian-bromann
The text was updated successfully, but these errors were encountered: