unable to run e2e tests with an empty project #13113

ismcagdas · 2018-12-02T08:08:28Z

Bug Report or Feature Request (mark with an `x`)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an `x`)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [x] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

node: 11.3.0
npm: 6.4.1
angular-cli: 7.1.0
windows: 10

Repro steps

Create a new project with ng new project-name and then run ng e2e

The log given by the failure

PS C:\Temp\myuitest\myiutest> ng e2e
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

Date: 2018-12-02T08:04:37.191Z
Hash: 5adaf35be360cda93f06
Time: 10268ms
chunk {main} main.js, main.js.map (main) 11.5 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 223 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 16.4 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 3.67 MB [initial] [rendered]
i ｢wdm｣: Compiled successfully.
[11:04:38] I/update - chromedriver: file exists C:\Temp\myuitest\myiutest\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_2.44.zip
[11:04:38] I/update - chromedriver: unzipping chromedriver_2.44.zip
[11:04:38] I/update - chromedriver: chromedriver_2.44.exe up to date
events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at ChildProcess.target._send (internal/child_process.js:758:20)
    at ChildProcess.target.send (internal/child_process.js:642:19)
    at Observable.rxjs_1.Observable.obs [as _subscribe] (C:\Temp\myuitest\myiutest\node_modules\@angular-devkit\build-angular\src\utils\run-module-as-observable-fork.js:57:23)
    at Observable._trySubscribe (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\Observable.js:44:25)
    at Observable.subscribe (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\Observable.js:30:22)
    at C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\util\subscribeTo.js:22:31
    at Object.subscribeToResult (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\util\subscribeToResult.js:10:45)
    at MergeMapSubscriber._innerSub (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\operators\mergeMap.js:82:29)
    at MergeMapSubscriber._tryNext (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\operators\mergeMap.js:76:14)
    at MergeMapSubscriber._next (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\operators\mergeMap.js:59:18)
    at MergeMapSubscriber.Subscriber.next (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\Subscriber.js:67:18)
    at MergeMapSubscriber.notifyNext (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\operators\mergeMap.js:92:26)
    at InnerSubscriber._next (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\InnerSubscriber.js:28:21)
    at InnerSubscriber.Subscriber.next (C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\Subscriber.js:67:18)
    at C:\Temp\myuitest\myiutest\node_modules\rxjs\internal\util\subscribeToPromise.js:7:24
    at process.internalTickCallback (internal/process/next_tick.js:77:7)
Emitted 'error' event at:
    at process.nextTick (internal/child_process.js:762:39)
    at process.internalTickCallback (internal/process/next_tick.js:70:11)
PS C:\Temp\myuitest\myiutest>

Mention any other details that might be useful

I have tried running ng e2e --webdriver-update=false but got the same error.

Thanks,

The text was updated successfully, but these errors were encountered:

itsUndefined · 2018-12-02T11:11:11Z

Downgrading nodeJS version to LTS fixes the issue. You could try that for now.

ismcagdas · 2018-12-02T19:20:22Z

Thanks a lot @itsUndefined 😄 it worked for me.

vitaly-t · 2018-12-04T17:18:46Z

Downgrading from the latest Node.js v11.x to the latest v10.x worked for me.

dmacfarlane · 2018-12-13T16:48:10Z

I got the same error on Node.js 10.14.2, downgrading to 10.14.1 worked for me.

HamedFathi · 2018-12-14T18:27:43Z

I got the same error too. 👎

Pluckerpluck · 2018-12-19T13:19:08Z

Same issue. 11.x and 10.14.2 do not work for me. 10.14.1 works fine.

Not the best start to trying out Angular for the first time...

Local9 · 2018-12-20T16:08:23Z

Same issue, took ages to find out what it was. Can confirm the issue showed with node 10.14.2.

…cess Fix angular#13113

filipesilva · 2018-12-21T13:22:22Z

Heya all, we have a fix incoming in #13272.

…cess Fix #13113

bcaure · 2019-01-02T08:00:11Z

For Angular 6 users, upgrading Node to latest LTS (10.15.0) is working

amchess · 2019-01-03T16:50:34Z

For Angular 6 users, upgrading Node to latest LTS (10.15.0) is working

Angular CLI 6.2.8 (latest 6)
Node 10.15.0

ng e2e yet not working (Error: write EPIPE)

gowthaman-murugan · 2019-01-04T07:03:43Z

ng e2e yet not working (Error: write EPIPE)

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

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.8.8
@angular-devkit/build-angular     0.11.4
@angular-devkit/build-optimizer   0.11.4
@angular-devkit/build-webpack     0.11.4
@angular-devkit/core              0.8.8
@angular-devkit/schematics        0.8.8
@angular/cli                      6.2.8
@ngtools/webpack                  7.1.4
@schematics/angular               0.8.8
@schematics/update                0.8.8
rxjs                              6.2.2
typescript                        2.9.2
webpack                           4.23.1

Error


 PS D:\my-system\repo\my-application> ng e2e
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

Date: 2019-01-04T06:52:58.359Z
Hash: 31347b13f7dc17929426
Time: 11691ms
chunk {main} main.js, main.js.map (main) 66.6 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 223 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered]
chunk {scripts} scripts.js, scripts.js.map (scripts) 163 kB  [rendered]
chunk {styles} styles.js, styles.js.map (styles) 917 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 4.61 MB [initial] [rendered]
[12:22:58] I/file_manager - creating folder D:\my-system\repo\my-application\node_modules\protractor\node_modules\webdriver-manager\selenium
[12:22:58] I/config_source - curl -oD:\my-system\repo\my-application\node_modules\protractor\node_modules\webdriver-manager\selenium\chrome-response.xml https://chromedriver.storage.googleapis.com/
i ｢wdm｣: Compiled successfully.
[12:23:03] I/downloader - curl -oD:\my-system\repo\my-application\node_modules\protractor\node_modules\webdriver-manager\selenium/chromedriver_2.45.zip https://chromedriver.storage.googleapis.com/2.45/chromedriver_win32.zip
[12:23:43] I/update - chromedriver: unzipping chromedriver_2.45.zip
events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at ChildProcess.target._send (internal/child_process.js:742:20)
    at ChildProcess.target.send (internal/child_process.js:626:19)
    at Observable.rxjs_1.Observable.obs [as _subscribe] (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\src\utils\run-module-as-observable-fork.js:57:23)
    at Observable._trySubscribe (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\Observable.js:44:25)
    at Observable.subscribe (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\Observable.js:30:22)
    at D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\util\subscribeTo.js:22:31
    at Object.subscribeToResult (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\util\subscribeToResult.js:10:45)
    at MergeMapSubscriber._innerSub (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\operators\mergeMap.js:82:29)
    at MergeMapSubscriber._tryNext (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\operators\mergeMap.js:76:14)
    at MergeMapSubscriber._next (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\operators\mergeMap.js:59:18)
    at MergeMapSubscriber.Subscriber.next (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\Subscriber.js:67:18)
    at MergeMapSubscriber.notifyNext (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\operators\mergeMap.js:92:26)
    at InnerSubscriber._next (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\InnerSubscriber.js:28:21)
    at InnerSubscriber.Subscriber.next (D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\Subscriber.js:67:18)
    at D:\my-system\repo\my-application\node_modules\@angular-devkit\build-angular\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:746:39)
    at process._tickCallback (internal/process/next_tick.js:61:11)

filipesilva · 2019-01-04T09:18:33Z

The fix we merged should be in in the next patch release of the build system (@angular-devkit/build-angular@0.11.5), which isn't out yet.

gowthaman-murugan · 2019-01-04T13:26:51Z

@filipesilva Thank you for the quick response, but when we expect this version, I get another audit issue in "@angular-devkit/build-angular@0.11.4"


`-- @angular-devkit/build-angular@0.11.4

PS D:\my-system\repo\my-application> npm audit

                       === npm audit security report ===


                                 Manual Review
             Some vulnerabilities require your attention to resolve

          Visit https://go.npm.me/audit-guide for additional guidance


  High            Missing Origin Validation

  Package         webpack-dev-server

  Patched in      >=3.1.11

  Dependency of   @angular-devkit/build-angular [dev]

  Path            @angular-devkit/build-angular > webpack-dev-server

  More info       https://nodesecurity.io/advisories/725

found 1 high severity vulnerability in 38956 scanned packages
  1 vulnerability requires manual review. See the full report for details.

filipesilva · 2019-01-04T18:18:10Z

I think next week.

prajaktashah · 2019-01-07T06:58:19Z

working with node version 10.14.1, seems issue with chrome driver in 10.15.1 version.

YuliyaY · 2019-01-09T11:27:09Z

Node 10.15.1 and angular 7.2 -> had the same error
Downgraded node to 10.14.1 -> worked

mugshepherd · 2019-03-01T11:52:15Z

Node 10.15.1 and Angular 6.1.10. and had same error.
Downgrading to Node 10.14.1 worked for me.

doggy8088 · 2019-03-07T07:23:28Z

@filipesilva I think this might have a regression issue.
I can confirm Node 10.15.1 and Angular CLI 7.3.3 had the same error. When downgraded to Node to 10.14.1 just works!

doggy8088 · 2019-03-15T10:40:16Z

@Kiku-git Will you send a PR to angular-cli repo?

kritikatyayan · 2019-04-03T11:54:06Z

WORKED FOR WINDOWS 10

Install the current version using nvmw

nvmw install v10.14.2 <write your system version instead of 10.14.2>
nvmw install v8.4.2 <write version to be installed instead of 8.4.2>
nvmw ls
nvm use v8.9.4
node -v

You are good to go if it shows 8.9.4 !!!!

doggy8088 · 2019-04-07T15:18:02Z

I just confirmed that Node 10.15.1 solved this issue.

slavenl · 2019-04-17T12:49:39Z

I confirming that this error still occur on Node 10.15.3 with Angular CLI 7.3.8

jalchr · 2019-04-28T09:41:36Z

If ng e2e has such dependency on specific versions of node, wouldn't there be a version check when running this command and inform the developer properly ?

ng e2e
You current version of node is xx.xxx.xx, you should use at most version yyy.yyyy.yyyyy

LiorSaadon · 2019-05-12T14:46:07Z

Error still occur on windows10
Node 10.15.3 with Angular CLI 7.0.4

MacGyver214-zz · 2019-05-14T16:49:01Z

@LiorSaadon and anyone else still experiencing issues -- you need to run npm install @angular-devkit/build-angular@latest with the latest stable Angular CLI and Node versions. I can't confirm that it will work with Angular CLI v7.0.4 but I confirmed this morning that my tests pass with the following:

Angular CLI: 7.3.9
Node: 10.15.3
OS: win32 x64
Angular: 7.2.15
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.9
@angular-devkit/build-angular     0.13.9
@angular-devkit/build-optimizer   0.13.9
@angular-devkit/build-webpack     0.13.9
@angular-devkit/core              7.3.9
@angular-devkit/schematics        7.3.9
@angular/cdk                      7.3.7
@angular/cli                      7.3.9
@angular/material                 7.3.7
@angular/pwa                      0.13.7
@ngtools/webpack                  7.3.9
@schematics/angular               7.3.9
@schematics/update                0.13.9
rxjs                              6.5.1
typescript                        3.2.4
webpack                           4.29.0

6 scenarios (6 passed)
18 steps (18 passed)
0m10.145s

LiorSaadon · 2019-05-15T07:24:02Z

@macgyver214 - your fix works for me, thanks!

EndersonCezano · 2019-07-04T22:52:32Z

Node 10.16.0 and Angular 6.1.10 and had same error.
Downgrading to Node 10.14.1 worked for me.

Worked from Windows 10
Angular CLI: 6.0.8
Node: 10.4.1
OS: win32 x64
Angular: 6.1.10

angular-automatic-lock-bot · 2019-09-09T17:41:25Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

filipesilva added a commit to filipesilva/angular-cli that referenced this issue Dec 21, 2018

fix(@angular-devkit/build-angular): resolve project root for fork pro…

3b04e89

…cess Fix angular#13113

filipesilva mentioned this issue Dec 21, 2018

fix(@angular-devkit/build-angular): resolve project root for fork pro… #13272

Merged

hansl closed this as completed in #13272 Dec 26, 2018

hansl pushed a commit that referenced this issue Dec 26, 2018

fix(@angular-devkit/build-angular): resolve project root for fork pro…

3b52fa4

…cess Fix #13113

hansl pushed a commit that referenced this issue Dec 26, 2018

fix(@angular-devkit/build-angular): resolve project root for fork pro…

a43e9fa

…cess Fix #13113

peterennis mentioned this issue Jan 6, 2019

unable to run e2e tests with simple project #13376

Closed

arawinters mentioned this issue Jun 13, 2019

Fix e2e tests senzing-garage/sdk-components-ng#55

Closed

niklas-wortmann mentioned this issue Jul 10, 2019

test(docs): add visual testing using applitools ReactiveX/rxjs#4872

Merged

ghost mentioned this issue Jul 22, 2019

events.js:174 throw er; -> Error: write EPIPE angular/protractor#5283

Closed

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

unable to run e2e tests with an empty project #13113

unable to run e2e tests with an empty project #13113

ismcagdas commented Dec 2, 2018

itsUndefined commented Dec 2, 2018

ismcagdas commented Dec 2, 2018

vitaly-t commented Dec 4, 2018

dmacfarlane commented Dec 13, 2018

HamedFathi commented Dec 14, 2018

Pluckerpluck commented Dec 19, 2018 •

edited

Local9 commented Dec 20, 2018

filipesilva commented Dec 21, 2018

bcaure commented Jan 2, 2019

amchess commented Jan 3, 2019

gowthaman-murugan commented Jan 4, 2019 •

edited

filipesilva commented Jan 4, 2019 •

edited

gowthaman-murugan commented Jan 4, 2019 •

edited

filipesilva commented Jan 4, 2019

prajaktashah commented Jan 7, 2019

YuliyaY commented Jan 9, 2019

mugshepherd commented Mar 1, 2019

doggy8088 commented Mar 7, 2019 •

edited

doggy8088 commented Mar 15, 2019

kritikatyayan commented Apr 3, 2019

doggy8088 commented Apr 7, 2019

slavenl commented Apr 17, 2019

jalchr commented Apr 28, 2019

LiorSaadon commented May 12, 2019

MacGyver214-zz commented May 14, 2019

LiorSaadon commented May 15, 2019

EndersonCezano commented Jul 4, 2019

angular-automatic-lock-bot bot commented Sep 9, 2019

unable to run e2e tests with an empty project #13113

unable to run e2e tests with an empty project #13113

Comments

ismcagdas commented Dec 2, 2018

Bug Report or Feature Request (mark with an x)

Command (mark with an x)

Versions

Repro steps

The log given by the failure

Mention any other details that might be useful

itsUndefined commented Dec 2, 2018

ismcagdas commented Dec 2, 2018

vitaly-t commented Dec 4, 2018

dmacfarlane commented Dec 13, 2018

HamedFathi commented Dec 14, 2018

Pluckerpluck commented Dec 19, 2018 • edited

Local9 commented Dec 20, 2018

filipesilva commented Dec 21, 2018

bcaure commented Jan 2, 2019

amchess commented Jan 3, 2019

gowthaman-murugan commented Jan 4, 2019 • edited

filipesilva commented Jan 4, 2019 • edited

gowthaman-murugan commented Jan 4, 2019 • edited

filipesilva commented Jan 4, 2019

prajaktashah commented Jan 7, 2019

YuliyaY commented Jan 9, 2019

mugshepherd commented Mar 1, 2019

doggy8088 commented Mar 7, 2019 • edited

doggy8088 commented Mar 15, 2019

kritikatyayan commented Apr 3, 2019

doggy8088 commented Apr 7, 2019

slavenl commented Apr 17, 2019

jalchr commented Apr 28, 2019

LiorSaadon commented May 12, 2019

MacGyver214-zz commented May 14, 2019

LiorSaadon commented May 15, 2019

EndersonCezano commented Jul 4, 2019

angular-automatic-lock-bot bot commented Sep 9, 2019

Bug Report or Feature Request (mark with an `x`)

Command (mark with an `x`)

Pluckerpluck commented Dec 19, 2018 •

edited

gowthaman-murugan commented Jan 4, 2019 •

edited

filipesilva commented Jan 4, 2019 •

edited

gowthaman-murugan commented Jan 4, 2019 •

edited

doggy8088 commented Mar 7, 2019 •

edited