🐛 Bug: mocha fails with spawn EINVAL
on windows with node 22
#5162
Labels
status: waiting for author
waiting on response from OP - more information needed
type: bug
a defect, confirmed by a maintainer
Bug Report Checklist
faq
label, but none matched my issue.Expected
Tests with mochajs successfully start to execute without errors on GHA CI on windows
Actual
CI fails with:
Running "mochacli:test" (mochacli) task Warning: spawn EINVAL Use --force to continue. Aborted due to warnings.
Tests are not even started to execute.
Example of failed pipeline: https://github.com/objectionary/eo2js/actions/runs/9693490408/job/26749043096
Minimal, Reproducible Example
I run just regular
js
tests via GHA on windows usingGruntfile.js
:regular.test.js:
Versions
Full CI script is here
Additional Info
My little research tells me that issue is related to April node security release and can be resolved by passing
{ shell: true }
option tospawn
function. But here there's no such option. I think the problem may be hereThe text was updated successfully, but these errors were encountered: