not-test onProcessExit: process exit with code=127

[201flaviosilva]

Environment

1. vscode-jest version: v4.4.0
2. node -v: v17.1.0
3. npm -v: 8.1.4
4. npm ls jest: jest@28.1.0
5. your vscode-jest settings if customized: https://github.com/201flaviosilva/HillClimbing.js/blob/main/jest.config.js
6. Operating system: Mac OS Monterey 12.3.1 (21E258)

Prerequisite

• are you able to run jest test from the command line? Yes
• how do you run your tests from the command line? npm run test or npm run start:test

Steps to Reproduce

This is my working repository: https://github.com/201flaviosilva/HillClimbing.js

Relevant Debug Info

not-test onProcessExit: process exit with code=127, signal=undefined
 see troubleshooting: https://github.com/jest-community/vscode-jest/blob/master/README.md#troubleshooting
env: node: No such file or directory
Jest process "watch-tests" ended unexpectedly
 see troubleshooting: https://github.com/jest-community/vscode-jest/blob/master/README.md#troubleshooting

Expected Behavior

To run the test with any problem

Actual Behavior

Not run the tests and print this error:

[201flaviosilva]

Got a new error:

If this helps any way :)

[connectdotz]

env: node: No such file or directory

this is an indication that the shell env is not properly initialized. Try to start vscode from a terminal (instead of UI).

more detailed info here

[201flaviosilva]

Opening the VS Code this way has improved, but I don't think it's an intuitive way

[connectdotz]

indeed, I am hoping to come up with a better fix soon. I will let you know when it is available.

The link provided above (#741 (comment)) suggested a few workarounds, you can choose the one least sucked for now 😬

[201flaviosilva]

Yap, I think I will wait until it’s solved :)

[levrik]

I'm having the same issue but lacking env: node: No such file or directory in the logs. It's just not-test onProcessExit: process exit with code=127, signal=undefined without further logs.