Skip to content
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

Failed in "npm run test" #765

Closed
gzx-miller opened this issue Jul 14, 2020 · 6 comments
Closed

Failed in "npm run test" #765

gzx-miller opened this issue Jul 14, 2020 · 6 comments

Comments

@gzx-miller
Copy link

14 verbose lifecycle [email protected]test: CWD: D:\DCode\electron\node-addon-api
15 silly lifecycle [email protected]
test: Args: [ '/d /s /c', 'node test' ]
16 silly lifecycle [email protected]test: Returned: code: 9 signal: null
17 info lifecycle [email protected]
test: Failed to exec test script
18 verbose stack Error: [email protected] test: node test
18 verbose stack Exit status 9
18 verbose stack at EventEmitter. (C:\Users\guozhenxing\AppData\Roaming\nvm\v8.17.0\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
18 verbose stack at emitTwo (events.js:126:13)
18 verbose stack at EventEmitter.emit (events.js:214:7)
18 verbose stack at ChildProcess. (C:\Users\guozhenxing\AppData\Roaming\nvm\v8.17.0\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
18 verbose stack at emitTwo (events.js:126:13)
18 verbose stack at ChildProcess.emit (events.js:214:7)
18 verbose stack at maybeClose (internal/child_process.js:915:16)
18 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
19 verbose pkgid [email protected]
20 verbose cwd D:\DCode\electron\node-addon-api
21 verbose Windows_NT 10.0.18362
22 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "test"
23 verbose node v8.17.0
24 verbose npm v6.13.4
25 error code ELIFECYCLE
26 error errno 9
27 error [email protected] test: node test
27 error Exit status 9
28 error Failed at the [email protected] test script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 9, true ]

@gzx-miller
Copy link
Author

I use node 10.14.1, find same issue.
18 verbose stack Error: [email protected] test: node test
18 verbose stack Exit status 3221226356
18 verbose stack at EventEmitter. (C:\Users\guozhenxing\AppData\Roaming\nvm\v10.14.2\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
18 verbose stack at EventEmitter.emit (events.js:182:13)
18 verbose stack at ChildProcess. (C:\Users\guozhenxing\AppData\Roaming\nvm\v10.14.2\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
18 verbose stack at ChildProcess.emit (events.js:182:13)
18 verbose stack at maybeClose (internal/child_process.js:962:16)
18 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
19 verbose pkgid [email protected]
20 verbose cwd D:\DCode\electron\node-addon-api
21 verbose Windows_NT 10.0.18362
22 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "test"
23 verbose node v10.14.2
24 verbose npm v6.4.1
25 error code ELIFECYCLE
26 error errno 3221226356
27 error [email protected] test: node test
27 error Exit status 3221226356
28 error Failed at the [email protected] test script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 3221226356, true ]

@bzoz
Copy link

bzoz commented Jul 14, 2020

Can Cannot reproduce with either 12.18.2 and 14.5.0, with VS2019

Please provide:

  • entire --verbose log, put it inside backticks, like so:
```
log goes here
```

include the command that was used to run the test

  • Node version, system version

Did you:

  • run npm install?
  • run npm config set msvs_version [version you are using here]?
  • install MS Build Tools or Visual Studio?

@mhdawson
Copy link
Member

@bzoz mentioned more info would be helpful. Ideally enough so that we can add a test that would catch the failure in the future as current CI seems to be green: https://ci.nodejs.org/view/x%20-%20Abi%20stable%20module%20API/job/node-test-node-addon-api-LTS%20versions/

@NickNaso
Copy link
Member

NickNaso commented Jul 15, 2020

Hi @bzoz,
thanks for reporting the problem. Is your project public? Could you post your binding.gyp configuration ?

@NickNaso
Copy link
Member

This issue should be solved by the PR #766 or reverting the changes made by #757

@NickNaso
Copy link
Member

I'm closing because the v3.0.2 has been released and it should solve the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants