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

Trying to install cypress without a TTY produces thousands of lines of output during 'Unzipping Cypress' #1243

Open
jwalton opened this issue Feb 1, 2018 · 22 comments

Comments

@jwalton
Copy link

@jwalton jwalton commented Feb 1, 2018

Current behavior:

cypress

Desired behavior:

Installing cypress should print, like, five lines tops. Certainly less than a screen full.

How to reproduce:

The easiest way:

docker run --rm node:8.9.4-alpine npm install cypress

Current workaround

Set environment variable CI=1 to avoid a lot of output during install

@KittyGiraudel
Copy link
Contributor

@KittyGiraudel KittyGiraudel commented Feb 5, 2018

Maybe related: #817?

@ondrejbartas
Copy link

@ondrejbartas ondrejbartas commented Feb 14, 2018

@jwalton I was able to suppress output by CI=true npm install cypress which will produce only:

Installing Cypress (version: 1.4.2)

[10:27:23]  Downloading Cypress     [started]
[10:27:52]  Downloading Cypress     [completed]
[10:27:52]  Unzipping Cypress       [started]
...
@bahmutov
Copy link
Contributor

@bahmutov bahmutov commented Jun 26, 2018

Same problem for Netlify installs

screen shot 2018-06-25 at 11 40 20 pm

@kayvanbree
Copy link

@kayvanbree kayvanbree commented Jun 28, 2018

This is pretty annoying. It fills up the complete log with kinda useless information.

@martpie
Copy link

@martpie martpie commented Aug 8, 2018

@ondrejbartas This is unfortunately not a (optimal) solution as it may affect other part of your code/build by setting this CI environment variable to true.

@Christilut
Copy link

@Christilut Christilut commented Aug 30, 2018

Same problem here on Netlify. Also the unzipping stage takes about 10 minutes on Netlify but that's probably something on their end.

@bahmutov
Copy link
Contributor

@bahmutov bahmutov commented Aug 30, 2018

@Christilut you can find my Cypress + Netlify demo described at https://glebbahmutov.com/blog/gatsby-netlify-circle-and-cypress/

I did have to use CI=1 environment variable to get around lots of output during install, but I felt the deploy was quite snappy.

@shanecav
Copy link

@shanecav shanecav commented Nov 14, 2018

I'm running into the same issue on Netlify. Every build is failing because of their 15 minute limit, most of which is taken up by "Unzipping Cypress".

@martpie
Copy link

@martpie martpie commented Nov 14, 2018

I use Docker to build my app, but I don’t want to run my tests there: what I did is to move Cypress to optionalDependencies and npm install --no-optional.

Downloading and Unzipping just takes too much time...

@cymen
Copy link

@cymen cymen commented Dec 21, 2018

This is making our npm install take 2.5 minutes instead of 1 minute. I used the CI=true to fix it for now but it would be great to default to not logging this information.

@jennifer-shehane jennifer-shehane changed the title Trying to install cypress without a TTY produces thousands of lines of output Trying to install cypress without a TTY produces thousands of lines of output during 'Unzipping Cypress' Dec 26, 2018
@bussyjd
Copy link

@bussyjd bussyjd commented Feb 6, 2019

This fills up my cloudbuild log buffer on GCP CloudBuilder and I cannot see what happens afterwards.
This behavior is buggy and an environment variable CI=true to fix it is not okay, that's one layer everyone's Docker image for a single poor design choice

@Songyu-Wang
Copy link
Contributor

@Songyu-Wang Songyu-Wang commented Feb 23, 2019

@jennifer-shehane I dont think we should close this issue, The PR I created only reduce the number of prints, but it does not completely solve the problem

@jennifer-shehane
Copy link
Member

@jennifer-shehane jennifer-shehane commented Feb 25, 2019

@Songyu-Wang Thanks for clarifying!

camille-hdl added a commit to camille-hdl/cuisine-ead that referenced this issue Mar 13, 2019
@eddyekofo94
Copy link

@eddyekofo94 eddyekofo94 commented Sep 7, 2019

Still having this. issue Any update?

v1v added a commit to v1v/kibana that referenced this issue Nov 26, 2019
maxwell-k added a commit to maxwell-k/LumoSQL that referenced this issue Feb 21, 2020
Based on suggestions from:
cypress-io/cypress#1243
maxwell-k added a commit to maxwell-k/LumoSQL that referenced this issue Feb 21, 2020
maxwell-k added a commit to maxwell-k/LumoSQL that referenced this issue Feb 21, 2020
Installing and verifying cypress under act succeeds.

Reduce output from cypress install, based on suggestions from:
cypress-io/cypress#1243
maxwell-k added a commit to maxwell-k/LumoSQL that referenced this issue Feb 24, 2020
Installing, verify and run cypress under act successfully.

Reduce output from cypress install, based on suggestions from:
cypress-io/cypress#1243
maxwell-k added a commit to maxwell-k/LumoSQL that referenced this issue Feb 24, 2020
Installing, verify and run cypress under act successfully.

Reduce output from cypress install, based on suggestions from:
cypress-io/cypress#1243
maxwell-k added a commit to maxwell-k/LumoSQL that referenced this issue Feb 26, 2020
Installing, verify and run cypress under act successfully.

Reduce output from cypress install, based on suggestions from:
cypress-io/cypress#1243
maxwell-k added a commit to maxwell-k/LumoSQL that referenced this issue Feb 26, 2020
Installing, verify and run cypress under act successfully.

Reduce output from cypress install, based on suggestions from:
cypress-io/cypress#1243
@mike-potter
Copy link

@mike-potter mike-potter commented Apr 2, 2020

Any resolution on this? Using ci=true is not an option as that kills build performance by deleting the node_modules folder and starting npm-install from scratch. We are already using the npm install --quiet flag and should ONLY be seeing errors and warnings. The huge cypress "Downloading" and "Unzipping" messages are neither. Cypress should be respecting the --quiet flag.

@bahmutov
Copy link
Contributor

@bahmutov bahmutov commented Apr 2, 2020

@mike-potter the work around we put at the top of the issue is not to do npm ci but to set the environment variable CI=1 when doing any type of install. For example you could do CI=1 npm install or CI=1 yarn to prevent extra messages

@mike-potter
Copy link

@mike-potter mike-potter commented Apr 3, 2020

Can somebody point me to the docs for the CI environment variable? Is this something npm is using, or is this Cypress-specific. I need to know what the other affects of setting this variable might be before I can add it to our prod deployment.

@mike-potter
Copy link

@mike-potter mike-potter commented Apr 3, 2020

Also, since this job is running in GitLab, I can see that there is already a global environment variable CI=true being set, so not sure putting this inline with the npm install will change anything. Does it need to be CI=1 rather than CI=true?

@bahmutov
Copy link
Contributor

@bahmutov bahmutov commented Apr 3, 2020

@mike-potter
Copy link

@mike-potter mike-potter commented Apr 3, 2020

Bah, sorry, my fault. We were running npm install in docker-in-docker and the CI variable wasn't being passed down into that container.

@joshnuna
Copy link

@joshnuna joshnuna commented Apr 19, 2020

This issue has been open for over 2 years. I'm wondering what the business requirement that the percentage of an unzip need to be logged to stdout in any case, or has this made no progress in 2 years?

@jennifer-shehane
Copy link
Member

@jennifer-shehane jennifer-shehane commented Apr 23, 2020

This issue is still in the 'ready for work' stage, which means no work has been done on this issue as of today, so we do not have an estimate on when this will be delivered.

@joshnuna It is nice to see the install progress when installing locally. The printing of every progress line does not effect every user of Cypress nor every environment.

There is an existing workaround #1243 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment