cypress: EPIPE error on Windows runs

Bug

Cypress v3.0.1
Windows
Node 10.1.0
npm 6.1.0

Saw this error on AppVeyor Windows CI https://ci.appveyor.com/project/cypress-io/cypress-example-todomvc/build/1.0.169

events.js:167
      throw er; // Unhandled 'error' event
      ^
Error: shutdown EPIPE
    at ReadStream.Socket._final (net.js:369:25)
    at callFinal (_stream_writable.js:615:10)
    at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
    at ReadStream.onerror (_stream_readable.js:693:12)
    at ReadStream.emit (events.js:182:13)
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ cypress:run: `cypress run`

Maybe

a long request that’s still in flight and being proxied when the server shuts down (since the tests pass)
shutting down the http-server when there are open connections
killing the child processes (?)

Need to debug with DEBUG=cypress:* to isolate the problem

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 2
Comments: 36 (14 by maintainers)

Commits related to this issue

catch EPIPE errors (#2011) fixes #1841 — committed to cypress-io/cypress by brian-mann 6 years ago

Most upvoted comments

Guys, any news on this one? It’s pretty ugly one 😦

uoziod on Jun 18, 2018

Good news - was able to reproduce this, but only in some specific versions of node.

brian-mann on Jun 21, 2018

Yeah, I encountered this same issue today after going to 3.0.1. The tests all passed, but the build fails due to this issue.

AaronN-STCU on Jun 1, 2018

Released in 3.0.2.

brian-mann on Jun 29, 2018

Looking into this now…

brian-mann on Jun 21, 2018

@brian-mann Do you have any idea when this will be released?

vladjerca on Jun 22, 2018

Another Stack trace from TeamCity running on Windows. I simply updated Cypress (and restarted server for good measure). Same tests were running flawlessly until the update.

events.js:160
[10:36:36][Step 2/2]       throw er; // Unhandled 'error' event
[10:36:36][Step 2/2]       ^
[10:36:36][Step 2/2] 
[10:36:36][Step 2/2] Error: shutdown EPIPE
[10:36:36][Step 2/2]     at exports._errnoException (util.js:1018:11)
[10:36:36][Step 2/2]     at Socket.onSocketFinish (net.js:237:26)
[10:36:36][Step 2/2]     at emitNone (events.js:91:20)
[10:36:36][Step 2/2]     at Socket.emit (events.js:185:7)
[10:36:36][Step 2/2]     at finishMaybe (_stream_writable.js:515:14)
[10:36:36][Step 2/2]     at endWritable (_stream_writable.js:525:3)
[10:36:36][Step 2/2]     at Socket.Writable.end (_stream_writable.js:490:5)
[10:36:36][Step 2/2]     at Socket.end (net.js:431:31)
[10:36:36][Step 2/2]     at Socket.onend (_stream_readable.js:511:10)
[10:36:36][Step 2/2]     at Socket.g (events.js:291:16)
[10:36:36][Step 2/2]     at emitNone (events.js:91:20)
[10:36:36][Step 2/2]     at Socket.emit (events.js:185:7)
[10:36:36][Step 2/2]     at endReadableNT (_stream_readable.js:974:12)
[10:36:36][Step 2/2]     at _combinedTickCallback (internal/process/next_tick.js:80:11)
[10:36:36][Step 2/2]     at process._tickCallback (internal/process/next_tick.js:104:9)

richdom81 on Jun 5, 2018

I downgraded go cypress 2.1 and it ran on vsts!

Den ons 13 juni 2018 18:07maccurt notifications@github.com skrev:

I am seeing this error also on my jenkins run. I did just install cypress brand new globally because it was installing and unzipping every time, which was taking 5 minutes. Perhaps this newer version broke something or more likely I did something wrong. ha ha

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cypress-io/cypress/issues/1841#issuecomment-396994881, or mute the thread https://github.com/notifications/unsubscribe-auth/ABgKZ8DPuRezC6MKyl0TqKXFen4svrPzks5t8TjJgaJpZM4UVcyf .

stilren on Jun 13, 2018