How to fix crashing ng tests [on hold]
up vote
0
down vote
favorite
I have an Angular application set up. Everything works fine except when the test is run via ng test it runs all the test and all is fine, but instead of existing, it crashes with following errors:
[31m21 11 2018 20:48:44.267:ERROR [karma]: [39mTypeError: Cannot read property 'on' of undefined
at buildProcessTree (/Users/me/ui/node_modules/tree-kill/index.js:83:15)
at /Users/me/ui/node_modules/tree-kill/index.js:104:11
at Array.forEach (<anonymous>)
at ChildProcess.onClose (/Users/me/ui/node_modules/tree-kill/index.js:99:31)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
[36m21 11 2018 20:48:44.270:DEBUG [launcher]: [39mDisconnecting all browsers
[31m21 11 2018 20:48:44.271:ERROR [karma]: [39mTypeError: Cannot read property 'on' of undefined
at buildProcessTree (/Users/me/ui/node_modules/tree-kill/index.js:83:15)
at /Users/me/ui/node_modules/tree-kill/index.js:104:11
at Array.forEach (<anonymous>)
at ChildProcess.onClose (/Users/me/ui/node_modules/tree-kill/index.js:99:31)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
....
[36m21 11 2018 20:48:49.599:DEBUG [launcher]: [39mDisconnecting all browsers
[31m21 11 2018 20:48:49.599:ERROR [karma]: [39m{ Error: spawn pgrep EAGAIN
at _errnoException (util.js:992:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
at onErrorNT (internal/child_process.js:372:16)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
code: 'EAGAIN',
errno: 'EAGAIN',
syscall: 'spawn pgrep',
path: 'pgrep',
spawnargs: [ '-P', 2668 ] }
Not even sure where to start troubleshooting this problem. Details of my set up is as follows:
macOS Mojave
node --version
v8.11.3
npm --version
5.6.0
ng --version
Angular CLI: 7.0.5
Node: 8.11.3
OS: darwin x64
Angular: 7.0.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, upgrade
Package Version
@angular-devkit/architect 0.10.5
@angular-devkit/build-angular 0.10.5
@angular-devkit/build-optimizer 0.10.5
@angular-devkit/build-webpack 0.10.5
@angular-devkit/core 7.0.5
@angular-devkit/schematics 7.0.5
@angular/cli 7.0.5
@ngtools/webpack 7.0.5
@schematics/angular 7.0.5
@schematics/update 0.10.5
rxjs 6.3.3
typescript 3.1.6
webpack 4.19.1
Any suggestions/pointers on how to fix this problem, would be appreciated.
angular angular-cli
asked Nov 21 at 20:07
dade
1,39731832
put on hold as off-topic by R. Richards, Roman Pokrovskij, Nic3500, derHugo, aaaaaa123456789 Nov 22 at 10:00
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking debugging help ("why isn't this code working?") must include the desired behavior, a specific problem or error and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example." – R. Richards, Nic3500, derHugo, aaaaaa123456789
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
I have an Angular application set up. Everything works fine except when the test is run via ng test it runs all the test and all is fine, but instead of existing, it crashes with following errors:
[31m21 11 2018 20:48:44.267:ERROR [karma]: [39mTypeError: Cannot read property 'on' of undefined
at buildProcessTree (/Users/me/ui/node_modules/tree-kill/index.js:83:15)
at /Users/me/ui/node_modules/tree-kill/index.js:104:11
at Array.forEach (<anonymous>)
at ChildProcess.onClose (/Users/me/ui/node_modules/tree-kill/index.js:99:31)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
[36m21 11 2018 20:48:44.270:DEBUG [launcher]: [39mDisconnecting all browsers
[31m21 11 2018 20:48:44.271:ERROR [karma]: [39mTypeError: Cannot read property 'on' of undefined
at buildProcessTree (/Users/me/ui/node_modules/tree-kill/index.js:83:15)
at /Users/me/ui/node_modules/tree-kill/index.js:104:11
at Array.forEach (<anonymous>)
at ChildProcess.onClose (/Users/me/ui/node_modules/tree-kill/index.js:99:31)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
....
[36m21 11 2018 20:48:49.599:DEBUG [launcher]: [39mDisconnecting all browsers
[31m21 11 2018 20:48:49.599:ERROR [karma]: [39m{ Error: spawn pgrep EAGAIN
at _errnoException (util.js:992:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
at onErrorNT (internal/child_process.js:372:16)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
code: 'EAGAIN',
errno: 'EAGAIN',
syscall: 'spawn pgrep',
path: 'pgrep',
spawnargs: [ '-P', 2668 ] }
Not even sure where to start troubleshooting this problem. Details of my set up is as follows:
macOS Mojave
node --version
v8.11.3
npm --version
5.6.0
ng --version
Angular CLI: 7.0.5
Node: 8.11.3
OS: darwin x64
Angular: 7.0.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, upgrade
Package Version
@angular-devkit/architect 0.10.5
@angular-devkit/build-angular 0.10.5
@angular-devkit/build-optimizer 0.10.5
@angular-devkit/build-webpack 0.10.5
@angular-devkit/core 7.0.5
@angular-devkit/schematics 7.0.5
@angular/cli 7.0.5
@ngtools/webpack 7.0.5
@schematics/angular 7.0.5
@schematics/update 0.10.5
rxjs 6.3.3
typescript 3.1.6
webpack 4.19.1
Any suggestions/pointers on how to fix this problem, would be appreciated.
angular angular-cli
asked Nov 21 at 20:07
dade
1,39731832
put on hold as off-topic by R. Richards, Roman Pokrovskij, Nic3500, derHugo, aaaaaa123456789 Nov 22 at 10:00
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking debugging help ("why isn't this code working?") must include the desired behavior, a specific problem or error and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example." – R. Richards, Nic3500, derHugo, aaaaaa123456789
If this question can be reworded to fit the rules in the help center, please edit the question.
As you're using ng test, I assume you have a CLI project using Karma for testing. In this case, you could try changing logLevel to LOG_DEBUG (on karma.conf.js) to try to figure out what the issue is. You may find possible values for logLevel here
– GCSDC
Nov 22 at 0:18
the log level was changed to LOG_DEBUG, which is why I was able to get the first part of the stacktrace
– dade
Nov 22 at 2:50
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an Angular application set up. Everything works fine except when the test is run via ng test it runs all the test and all is fine, but instead of existing, it crashes with following errors:
[31m21 11 2018 20:48:44.267:ERROR [karma]: [39mTypeError: Cannot read property 'on' of undefined
at buildProcessTree (/Users/me/ui/node_modules/tree-kill/index.js:83:15)
at /Users/me/ui/node_modules/tree-kill/index.js:104:11
at Array.forEach (<anonymous>)
at ChildProcess.onClose (/Users/me/ui/node_modules/tree-kill/index.js:99:31)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
[36m21 11 2018 20:48:44.270:DEBUG [launcher]: [39mDisconnecting all browsers
[31m21 11 2018 20:48:44.271:ERROR [karma]: [39mTypeError: Cannot read property 'on' of undefined
at buildProcessTree (/Users/me/ui/node_modules/tree-kill/index.js:83:15)
at /Users/me/ui/node_modules/tree-kill/index.js:104:11
at Array.forEach (<anonymous>)
at ChildProcess.onClose (/Users/me/ui/node_modules/tree-kill/index.js:99:31)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
....
[36m21 11 2018 20:48:49.599:DEBUG [launcher]: [39mDisconnecting all browsers
[31m21 11 2018 20:48:49.599:ERROR [karma]: [39m{ Error: spawn pgrep EAGAIN
at _errnoException (util.js:992:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
at onErrorNT (internal/child_process.js:372:16)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
code: 'EAGAIN',
errno: 'EAGAIN',
syscall: 'spawn pgrep',
path: 'pgrep',
spawnargs: [ '-P', 2668 ] }
Not even sure where to start troubleshooting this problem. Details of my set up is as follows:
macOS Mojave
node --version
v8.11.3
npm --version
5.6.0
ng --version
Angular CLI: 7.0.5
Node: 8.11.3
OS: darwin x64
Angular: 7.0.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, upgrade
Package Version
@angular-devkit/architect 0.10.5
@angular-devkit/build-angular 0.10.5
@angular-devkit/build-optimizer 0.10.5
@angular-devkit/build-webpack 0.10.5
@angular-devkit/core 7.0.5
@angular-devkit/schematics 7.0.5
@angular/cli 7.0.5
@ngtools/webpack 7.0.5
@schematics/angular 7.0.5
@schematics/update 0.10.5
rxjs 6.3.3
typescript 3.1.6
webpack 4.19.1
Any suggestions/pointers on how to fix this problem, would be appreciated.
angular angular-cli
asked Nov 21 at 20:07
dade
1,39731832
I have an Angular application set up. Everything works fine except when the test is run via ng test it runs all the test and all is fine, but instead of existing, it crashes with following errors:
[31m21 11 2018 20:48:44.267:ERROR [karma]: [39mTypeError: Cannot read property 'on' of undefined
at buildProcessTree (/Users/me/ui/node_modules/tree-kill/index.js:83:15)
at /Users/me/ui/node_modules/tree-kill/index.js:104:11
at Array.forEach (<anonymous>)
at ChildProcess.onClose (/Users/me/ui/node_modules/tree-kill/index.js:99:31)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
[36m21 11 2018 20:48:44.270:DEBUG [launcher]: [39mDisconnecting all browsers
[31m21 11 2018 20:48:44.271:ERROR [karma]: [39mTypeError: Cannot read property 'on' of undefined
at buildProcessTree (/Users/me/ui/node_modules/tree-kill/index.js:83:15)
at /Users/me/ui/node_modules/tree-kill/index.js:104:11
at Array.forEach (<anonymous>)
at ChildProcess.onClose (/Users/me/ui/node_modules/tree-kill/index.js:99:31)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
....
[36m21 11 2018 20:48:49.599:DEBUG [launcher]: [39mDisconnecting all browsers
[31m21 11 2018 20:48:49.599:ERROR [karma]: [39m{ Error: spawn pgrep EAGAIN
at _errnoException (util.js:992:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
at onErrorNT (internal/child_process.js:372:16)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
code: 'EAGAIN',
errno: 'EAGAIN',
syscall: 'spawn pgrep',
path: 'pgrep',
spawnargs: [ '-P', 2668 ] }
Not even sure where to start troubleshooting this problem. Details of my set up is as follows:
macOS Mojave
node --version
v8.11.3
npm --version
5.6.0
ng --version
Angular CLI: 7.0.5
Node: 8.11.3
OS: darwin x64
Angular: 7.0.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, upgrade
Package Version
@angular-devkit/architect 0.10.5
@angular-devkit/build-angular 0.10.5
@angular-devkit/build-optimizer 0.10.5
@angular-devkit/build-webpack 0.10.5
@angular-devkit/core 7.0.5
@angular-devkit/schematics 7.0.5
@angular/cli 7.0.5
@ngtools/webpack 7.0.5
@schematics/angular 7.0.5
@schematics/update 0.10.5
rxjs 6.3.3
typescript 3.1.6
webpack 4.19.1
Any suggestions/pointers on how to fix this problem, would be appreciated.
angular angular-cli
angular angular-cli
asked Nov 21 at 20:07
dade
1,39731832
asked Nov 21 at 20:07
dade
1,39731832
edited Nov 22 at 2:53
asked Nov 21 at 20:07
dade
1,39731832
asked Nov 21 at 20:07
dade
1,39731832
asked Nov 21 at 20:07
dade
1,39731832
1,39731832
put on hold as off-topic by R. Richards, Roman Pokrovskij, Nic3500, derHugo, aaaaaa123456789 Nov 22 at 10:00
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking debugging help ("why isn't this code working?") must include the desired behavior, a specific problem or error and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example." – R. Richards, Nic3500, derHugo, aaaaaa123456789
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by R. Richards, Roman Pokrovskij, Nic3500, derHugo, aaaaaa123456789 Nov 22 at 10:00
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking debugging help ("why isn't this code working?") must include the desired behavior, a specific problem or error and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example." – R. Richards, Nic3500, derHugo, aaaaaa123456789
If this question can be reworded to fit the rules in the help center, please edit the question.
As you're using ng test, I assume you have a CLI project using Karma for testing. In this case, you could try changing logLevel to LOG_DEBUG (on karma.conf.js) to try to figure out what the issue is. You may find possible values for logLevel here
– GCSDC
Nov 22 at 0:18
the log level was changed to LOG_DEBUG, which is why I was able to get the first part of the stacktrace
– dade
Nov 22 at 2:50
add a comment |
As you're using ng test, I assume you have a CLI project using Karma for testing. In this case, you could try changing logLevel to LOG_DEBUG (on karma.conf.js) to try to figure out what the issue is. You may find possible values for logLevel here
– GCSDC
Nov 22 at 0:18
the log level was changed to LOG_DEBUG, which is why I was able to get the first part of the stacktrace
– dade
Nov 22 at 2:50
As you're using ng test, I assume you have a CLI project using Karma for testing. In this case, you could try changing logLevel to LOG_DEBUG (on karma.conf.js) to try to figure out what the issue is. You may find possible values for logLevel here
– GCSDC
Nov 22 at 0:18
As you're using ng test, I assume you have a CLI project using Karma for testing. In this case, you could try changing logLevel to LOG_DEBUG (on karma.conf.js) to try to figure out what the issue is. You may find possible values for logLevel here
– GCSDC
Nov 22 at 0:18
the log level was changed to LOG_DEBUG, which is why I was able to get the first part of the stacktrace
– dade
Nov 22 at 2:50
the log level was changed to LOG_DEBUG, which is why I was able to get the first part of the stacktrace
– dade
Nov 22 at 2:50
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
As you're using ng test, I assume you have a CLI project using Karma for testing. In this case, you could try changing logLevel to LOG_DEBUG (on karma.conf.js) to try to figure out what the issue is. You may find possible values for logLevel here
– GCSDC
Nov 22 at 0:18
the log level was changed to LOG_DEBUG, which is why I was able to get the first part of the stacktrace
– dade
Nov 22 at 2:50