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

npm test error Executed 0 of 0 ERROR #1467

Open
WhiskyWonka opened this issue Dec 23, 2017 · 5 comments
Open

npm test error Executed 0 of 0 ERROR #1467

WhiskyWonka opened this issue Dec 23, 2017 · 5 comments

Comments

@WhiskyWonka
Copy link

Hello
npm install was ok but when i try to run test I have this error

npm test

[email protected] test C:\xampp\htdocs\projects\ngx-admin
ng test -sr

10% building modules 1/1 modules 0 active23 12 2017 08:52:24.808:INFO [karma]: Karma v2.0.0 server started at http://0.0.0.0:9876/
23 12 2017 08:52:24.808:INFO [launcher]: Launching browser Chrome with unlimited concurrency
23 12 2017 08:52:24.808:INFO [launcher]: Starting browser Chrome 23 12 2017 08:53:12.849:INFO [Chrome 63.0.3239 (Windows 10 0.0.0)]: Connected on socket aeCXCZrY5yvK0iZrAAAA with id 20468650
Chrome 63.0.3239 (Windows 10 0.0.0): Executed 0 of 0 ERROR (0.02 secs / 0 secs)
npm ERR! Test failed. See above for more details.

any idea?
Thank you

@dtzar
Copy link

dtzar commented Jun 14, 2018

This problem happens on mac OS X 10.13.5 with Chrome 67.0.3396 as well.
The problem still occurs even if you upgrade all of the karma* packages to the latest major versions.
npm run test:coverage is also broken due to the same problem.

@dpollastrini
Copy link

image

@nnixaa
Copy link
Collaborator

nnixaa commented Jun 30, 2018

Hey Guys, can someone consolidate a reproducible example?

@dpollastrini
Copy link

git clone [email protected]:akveo/ngx-admin ngx-admin-test
cd ngx-admin-test
git checkout starter-kit
npm install
npm run test

10% building modules 1/1 modules 0 active(node:10196) DeprecationWarning: Tapable.plugin is deprecated. Use new API on '.hooks' instead
30 06 2018 09:26:33.182:INFO [karma]: Karma v1.7.1 server started at http://0.0.0.0:9876/
30 06 2018 09:26:33.184:INFO [launcher]: Launching browser Chrome with unlimited concurrency
30 06 2018 09:26:33.188:INFO [launcher]: Starting browser Chrome                                                                                                                                                                     30 06 2018 09:26:37.108:INFO [Chrome 67.0.3396 (Windows 10.0.0)]: Connected on socket WzOeXYKmoQPHR2zCAAAA with id 28806449
Chrome 67.0.3396 (Windows 10.0.0): Executed 0 of 0 ERROR (0.006 secs / 0 secs)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] test: 'ng test'
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\dave.pollastrini\AppData\Roaming\npm-cache\_logs\2018-06-30T16_26_38_615Z-debug.log

Log file content:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'test' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'pretest', 'test', 'posttest' ]
5 info lifecycle [email protected]~pretest: [email protected]
6 info lifecycle [email protected]~test: [email protected]
7 verbose lifecycle [email protected]~test: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~test: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\dave.pollastrini\git\ngx-admin-test\node_modules\.bin;C:\Program Files\Docker\Docker\Resources\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\nodejs\;C:\WINDOWS\System32\OpenSSH\;C:\Users\dave.pollastrini\AppData\Local\Microsoft\WindowsApps;;C:\Program Files\Microsoft VS Code\bin;C:\Users\dave.pollastrini\.dotnet\tools;C:\Users\dave.pollastrini\AppData\Roaming\npm;%USERPROFILE%\AppData\Local\Microsoft\WindowsApps
9 verbose lifecycle [email protected]~test: CWD: C:\Users\dave.pollastrini\git\ngx-admin-test
10 silly lifecycle [email protected]~test: Args: [ '/d /s /c', 'ng test' ]
11 silly lifecycle [email protected]~test: Returned: code: 1  signal: null
12 info lifecycle [email protected]~test: Failed to exec test script
13 verbose stack Error: [email protected] test: `ng test`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:285:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\Users\dave.pollastrini\git\ngx-admin-test
16 verbose Windows_NT 10.0.17134
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "test"
18 verbose node v8.11.2
19 verbose npm  v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] test: `ng test`
22 error Exit status 1
23 error Failed at the [email protected] test script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Version info:

ng --version
Your global Angular CLI version (6.0.5) is greater than your local
version (6.0.0). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/


Angular CLI: 6.0.0
Node: 8.11.2
OS: win32 x64
Angular: 6.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.6.0
@angular-devkit/build-optimizer   0.6.0
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@ngtools/webpack                  6.0.0
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

@yggg
Copy link
Contributor

yggg commented Oct 9, 2018

Maybe related karma-runner/karma#753 (comment)

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

No branches or pull requests

5 participants