Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

not-test onProcessExit: process exit with code=127

See original GitHub issue

Environment

vscode-jest version: v4.4.0
node -v: v17.1.0
npm -v: 8.1.4
npm ls jest: jest@28.1.0
your vscode-jest settings if customized: https://github.com/201flaviosilva/HillClimbing.js/blob/main/jest.config.js
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:

Issue Analytics

State:
Created a year ago
Comments:6

Top GitHub Comments

1reaction

levrikcommented, Oct 6, 2022

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.

0reactions

201flaviosilvacommented, May 23, 2022

Yap, I think I will wait until it’s solved 😃

Top Results From Across the Web

Whenever I create a new file, the Jest extension ... - GitHub

... for Jest opens with an error. not-test-4 is scheduled not-test onProcessExit: process exit with code=127, signal=undefined see troubl...

stubbing process.exit with jest - Stack Overflow

Nice answer! PS: There is no need to pass an arrow function for mockImplementation unless you must set a variable on test scope...

npm install -> Error: Process completed with exit code 1-bash

It looks like something in your project is using node-sass, which contains libsass which is deprecated. If it is a direct dependency, you...

npmsearchfullcat_npm143.txt - GitHub

=btford 2013-07-29 0.0.2 testing test mock spy 06_byvoidmodule 你好 ... 123 123 =feitian 2013-12-20 0.0.1 123 127-ssh Capture your command not found and ......

Release notes — fish-shell 3.4.1 documentation

command -v returns an exit status of 127 instead of 1 if no command was found ... wait and on-process-exit work correctly with...