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

TypeError: Cannot read property 'pipe' of undefined #63

Open
gil13 opened this issue May 29, 2019 · 3 comments
Open

TypeError: Cannot read property 'pipe' of undefined #63

gil13 opened this issue May 29, 2019 · 3 comments

Comments

@gil13
Copy link

gil13 commented May 29, 2019

When its trying to re-execute failed test I always get this error

[13:09:27] E/launcher - Error: TypeError: Cannot read property 'pipe' of undefined at /Users/alberto/agent/_work/1/s/node_modules/protractor-retry/lib/retry.js:152:26 at Function.promise (/Users/alberto/agent/_work/1/s/node_modules/q/q.js:682:9) at /Users/alberto/agent/_work/1/s/node_modules/protractor-retry/lib/retry.js:150:18 at Promise.apply (/Users/alberto/agent/_work/1/s/node_modules/q/q.js:1165:26) at Promise.promise.promiseDispatch (/Users/alberto/agent/_work/1/s/node_modules/q/q.js:788:41) at /Users/alberto/agent/_work/1/s/node_modules/q/q.js:1391:14 at runSingle (/Users/alberto/agent/_work/1/s/node_modules/q/q.js:137:13) at flush (/Users/alberto/agent/_work/1/s/node_modules/q/q.js:125:13) at process._tickCallback (internal/process/next_tick.js:61:11)

Any idea ?

@zahnrodolfo
Copy link

I'm facing the same issue and what I could discover is that the child_process.spawn() command is not generating the stdio so the stdout and stderr are not created. This way you get pipe of undefined.

I'm not sure exactly what is causing this but I could replicate it and it gives me the ENOENT or EACCESS error in this exact command.

@dreuxl
Copy link
Contributor

dreuxl commented Jun 28, 2019

yep, I m not sure how that case can happen. never seen it. I would need to take a look.

@kabomi
Copy link

kabomi commented Jul 17, 2019

Are you using angular-cli? I had a similar issue. You could try to run protractor instead of ng. Probably you will need to run your app from another console too.

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