chore: add initial ecosystem plugin tests workflow#19643
Conversation
✅ Deploy Preview for docs-eslint canceled.
|
578c12d to
baa84df
Compare
nzakas
left a comment
There was a problem hiding this comment.
Thanks for getting started on this. Left some comments throughout.
|
Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update. |
Co-authored-by: Nicholas C. Zakas <nicholas@humanwhocodes.com>
|
Todo for self: noting https://github.com/eslint/eslint/pull/19643/files#r2068835929 at root level so I don't forget to file the issue. |
|
Oh, right! Sorry - after all the back-and-forth around direction I'd lost track of this. I'll get it up-to-date, address feedback, and re-request review once it's ready again. Edit: I remember now, I'd been waiting for resolution on #19643 (comment) too. I'll just resolve that thread since it's been a while. |
|
Well, since last review activity, several packages have started failing. Specifically:
These still pass:
Proposal: would the team be ok with me removing the currently-failing packages, with followup issues to add them back in? Failures keep popping up between long review periods and it's slow wack-a-mole fixing them. |
I think that's perfectly okay 👍 For |
| runCommand(["git", "checkout", pluginSettings.commit]); | ||
|
|
||
| // 3. Install the plugin's dependencies | ||
| runCommand(["pwd"]); |
There was a problem hiding this comment.
I'm testing on Windows and this doesn't seem to work because, in PowerShell pwd is a cmdlet alias rather than an executable. This is what I'm seeing:
Testing @eslint/css in ...\eslint\ecosystem\eslint-css
[@eslint/css] git clone https://github.com/eslint/css ...\eslint\ecosystem\eslint-css --depth 1
[@eslint/css] git fetch origin 5c1c6251a359d26d117171de3a1e258e2c15ded9
[@eslint/css] git checkout 5c1c6251a359d26d117171de3a1e258e2c15ded9
[@eslint/css] pwd
Failed: @eslint/css
Errors occurred while testing plugins:
@eslint/css: Error: spawnSync pwd ENOENT
at notFoundError (...\eslint\node_modules\cross-spawn\lib\enoent.js:6:26)
at Object.verifyENOENTSync (...\eslint\node_modules\cross-spawn\lib\enoent.js:48:16)
at spawn.spawnSync [as sync] (...\eslint\node_modules\cross-spawn\index.js:29:43)
at runCommand (file:///.../eslint/tools/test-ecosystem/index.mjs:62:24)
at runTests (file:///.../eslint/tools/test-ecosystem/index.mjs:90:2)
at async file:///.../eslint/tools/test-ecosystem/index.mjs:127:3
Not a blocker since the ecosystem tests run on Unix in CI, but it would still be nice to fix this for Windows compatibility if possible.
There was a problem hiding this comment.
Oh wait, cross-spawn uses the old cmd.exe shell on Windows, so instead of pwd, this could be just cd without arguments to print the current directory.
There was a problem hiding this comment.
I would definitely like to leave any Windows-specific work as a followup. 🫠
Co-authored-by: Francesco Trotta <github@fasttime.org> Co-authored-by: 루밀LuMir <rpfos@naver.com>
fasttime
left a comment
There was a problem hiding this comment.
LGTM, thanks! Leaving open for @lumirlumir to verify.
lumirlumir
left a comment
There was a problem hiding this comment.
I'm sorry for the delay. Everything looks good to me.
Thank you for your time and effort on this PR!
|
Whoop! Thanks everyone for reviewing - this was a lot of back-and-forth, and I'm really excited to see it finally land! |
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain: internal CI change; implements eslint/rfcs#127
What changes did you make? (Give an overview)
Fixes #19139.
Adds an initial
.github/workflows/ecosystem.ymland package script.Is there anything you'd like reviewers to focus on?