events.js:174 throw er; -> Error: write EPIPE
See original GitHub issueHi, I was recently updated to Windows 10 so I’m not entirely sure what changed between Win7 -> Win10 that caused my protractor tests to stop working. I was hoping someone could help me figure out or where to look to help debug this issue!
Bug report
- Node Version:
v10.16.0
- Protractor Version:
5.4.2
- Angular Version:
7.1.4
- Browser(s):
Firefox
- Operating System and Version:
Win10 x64 bit
- Your protractor configuration file:
exports.config = {
allScriptsTimeout: 120000,
specs: [
'./e2e/**/*.e2e-spec.ts'
],
suites: {
homepage: './e2e/homepage/**/*.e2e-spec.ts',
createProposal: './e2e/create-proposal/**/*.e2e-spec.ts',
updateProposal: './e2e/update-proposal/**/*.e2e-spec.ts',
summaryProposal: './e2e/summary-proposal/**/*.e2e-spec.ts',
costEstimator: './e2e/cost-estimator/**/*.e2e-spec.ts'
},
capabilities: {
// 'browserName': 'chrome'
browserName: 'firefox',
marionette: true,
acceptInsecureCerts : true,
},
SELENIUM_PROMISE_MANAGER: false,
getPageTimeOut: 30000,
directConnect: true,
baseUrl: 'http://localhost:8080/',
framework: 'jasmine',
jasmineNodeOpts: {
showColors: true,
defaultTimeoutInterval: 9999999,
print: function() {}
},
onPrepare() {
require('ts-node').register({
project: 'e2e/tsconfig.e2e.json'
});
jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
}
};
- A relevant example test:
ng e2e
- Output from running the test:
[10:53:46] E/downloader - undefined
[10:53:46] I/update - chromedriver: file exists C:\Infrastructure\Angular\idl-cost-diff\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_75.0.3770.140.zip
[10:53:46] I/update - chromedriver: unzipping chromedriver_75.0.3770.140.zip
[10:53:46] I/update - chromedriver: chromedriver_75.0.3770.140.exe up to date
events.js:174
throw er; // Unhandled 'error' event
^
Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:762:20)
at ChildProcess.target.send (internal/child_process.js:634:19)
at Observable.rxjs_1.Observable.obs [as _subscribe] (C:\Infrastructure\Angular\idl-cost-diff\node_modules\@angular-devkit\build-angular\src\utils\run-module-as-observable-fork.js:57:23)
at Observable._trySubscribe (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\Observable.js:44:25)
at Observable.subscribe (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\Observable.js:30:22)
at C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\util\subscribeTo.js:22:31
at Object.subscribeToResult (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\util\subscribeToResult.js:10:45)
at MergeMapSubscriber._innerSub (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\operators\mergeMap.js:82:29)
at MergeMapSubscriber._tryNext (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\operators\mergeMap.js:76:14)
at MergeMapSubscriber._next (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\operators\mergeMap.js:59:18)
at MergeMapSubscriber.Subscriber.next (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\Subscriber.js:67:18)
at MergeMapSubscriber.notifyNext (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\operators\mergeMap.js:92:26)
at InnerSubscriber._next (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\InnerSubscriber.js:28:21)
at InnerSubscriber.Subscriber.next (C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\Subscriber.js:67:18)
at C:\Infrastructure\Angular\idl-cost-diff\node_modules\rxjs\internal\util\subscribeToPromise.js:7:24
at process._tickCallback (internal/process/next_tick.js:68:7)
Emitted 'error' event at:
at process.nextTick (internal/child_process.js:766:39)
at process._tickCallback (internal/process/next_tick.js:61:11)
Issue Analytics
- State:
- Created 4 years ago
- Comments:7
Top Results From Across the Web
Node.js - events.js:154 throw err write EPIPE; Program Crashing
EPIPE : A write on a pipe, socket, or FIFO for which there is no process to read the data. Commonly encountered at...
Read more >How to Fix "throw er; // Unhandled 'error' event"?
npm run watch fails with a rather cryptic "throw er; // Unhandled 'error' event". Here is how I resolved it.
Read more >How to Fix “throw er; // Unhandled 'error' event”? - Medium
When I was trying to run localhost in react it gave me this. throw er; // Unhandled 'error' event. some errors are tricky...
Read more >what is a "write EPIPE" error? - Google Groups
In this situation couch gets the header by itself in a tcp packet. Then it returns a packet back with the 409 error....
Read more >Windows events js 174 throw er; //Unhandled 'error' event
Events js 174 throw er; // Unhandled 'error' event ^ Error: write EPIPE ... Error: Connection lost: The server closed the connection. at...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just tried node 12.13.0 and 13.1.0 and both versions exhibited the same “throw er” issue.
I am also getting the same issue with v12.16.1.