cypress: dest.end error crash during run exit on GitLab CI / Windows

Hello Jeniffer, I need you

i have same trouble.

I don’t use

Same here

Same with me. Been waiting for this to be fixed.

@jennifer-shehane I tried what you suggested above, but with no result. Even using Node 8.16, the error happens.

This issue seems to be related: https://github.com/cypress-io/cypress/issues/3863

Using git bash on windows with pre-commit causes this error but running cypress through git bash normally works which is odd

Can y’all confirm if you are using precommit hooks?

This also explains some possible fixes: https://github.com/typicode/husky/issues/459#issuecomment-485568858

I found a workaround to the problem, using “git bash” as the default “shell” for Git Lab Runner.

1. Change windows registry “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\gitlab-runner” so it looks like this:

C:\Program Files\Git\bin\bash.exe -c “/c/gitlab/gitlab-runner.exe run --working-directory /c/gitlab --config /c/gitlab/config.toml --service gitlab-runner”

2. Set the “builds_dir” path in the runner configuration file, config.toml, using default bash syntax. Example:

builds_dir = “/C/GitLab-Runner/builds/CI”

3. Also in the config.toml file, set bash (git bash) as the default shell.

executor = “shell” shell = “bash”

any news or eta on this issue?

Any update on this issue? I have the same issue too!

Same problem here… Fix please!

The failure is being thrown from the readable-stream package on this line of code. This is included in core Node as stream

Our Node version:

• 8.2.1

Your original comment seems to indicate this was introduced in version 3.0.0 of Cypress which was released on May 29, 2018.

This file had commits made to it May 21, 2018 - it is one of 3 files that require Node stream.

I suspect that this error was introduced in the commit above and only happens on Windows in GitLab.

I’ve seen some open issues concerning TTY in GitLab? That’s a wild guess that it’s related though.

I have the same problem, runs fine from terminal on my laptop running Ubuntu but exits with that error while running from command prompt on a Windows Server 2016 Jenkins node.

Same issue here with buddy.works and my local machine (Mac).

@jelsav did you apply the patch correctly - you need to remove existing pipe lines. I have tried the patch in https://circleci.com/gh/cypress-io/cypress-test-tiny/4442 and everything looks ok

here is my patch file patches/cypress+3.4.1.patch

diff --git a/node_modules/cypress/lib/exec/spawn.js b/node_modules/cypress/lib/exec/spawn.js
index ed13727..7748f19 100644
--- a/node_modules/cypress/lib/exec/spawn.js
+++ b/node_modules/cypress/lib/exec/spawn.js
@@ -138,8 +138,15 @@ module.exports = {
         child.on('close', resolve);
         child.on('error', reject);
 
-        child.stdin && child.stdin.pipe(process.stdin);
-        child.stdout && child.stdout.pipe(process.stdout);
+        if (child.stdin) {
+          debug('piping process STDIN into child STDIN')
+          process.stdin.pipe(child.stdin)
+        }
+
+        if (child.stdout) {
+          debug('piping child STDOUT to process STDOUT')
+          child.stdout.pipe(process.stdout)
+        }
 
         // if this is defined then we are manually piping for linux
         // to filter out the garbage

@bahmutov Thanks for the patch! After applying it, we didn’t encounter dest.end error while running Cypress E2E tests on GitLab’s CI / Windows.

From the other side, after applying a patch, we faced with a new problem with duplicate log entries on test execution. Please see the screenshot of a Job below:

Is there a way to avoid duplicate log entries?

Thanks.

@PCStefan Did you find any solution to the problem? I’ve tried other versions of Node ^ 8.0.0 and Cypress ^ 3.0.0, but it does not work, only Cypress version 2.1.0 works correctly with git runner in Windows.

Hello there. Any update on this issue?

We have the same issue too.

• Windows Server 2012 R2
• Node: 8.2.1
• npm: 6.2.0
• Gitlab CI Runner: 11.2.0

this is blocking for us. anyone managed to workaround this issue?

I have the same issue.

_stream_readable.js:511
    dest.end();
         ^

TypeError: dest.end is not a function
    at Socket.onend (_stream_readable.js:511:10)
    at Socket.g (events.js:292:16)
    at emitNone (events.js:91:20)
    at Socket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

I have exactly the same issue! I really would like a fix and start using this in my CI nightly build.

Not working in v3.0.3 either