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

Enormous amount of data getting generated in C:\Users\Bamboo\AppData\Roaming\Partitions folder #20435

Open
aditimalik22 opened this issue Mar 1, 2022 · 6 comments
Labels
existing workaround prevent-stale mark an issue so it is ignored by stale[bot] stage: needs investigating Someone from Cypress needs to look at this

Comments

@aditimalik22
Copy link

What would you like?

I'd like to be able to understand what data gets generated in the partition folder and how can we control it.
We have approximately 15 projects that are using Cypress. All these are hosted on the server and run on Bamboo. From time to time, there are files worth Gb(s) that get generated in the C:.Users\Bamboo\AppData\Roaming\Partitions folder.

As of now, we have to manually delete these files but we are looking for a long-term solution.

Videos are turned off for most projects. Is there any way to control the contents of this folder?

Why is this needed?

I want this because these files sometimes paralyze our server..

Other

No response

@sainthkh sainthkh added the stage: proposal 💡 No work has been done of this issue label Mar 7, 2022
@wimme
Copy link

wimme commented Apr 8, 2022

Not sure if it is the exact same issue, but on our CI machines (Jenkins) we see something similar:

C:\Users\BuildUser\AppData\Roaming\Cypress\cy\production\projects

This folder contains "appname-e2e-guid" folders (seems to be linked to our Nx Angular apps) with javascript bundles, in total 53 GB and growing.

We also have this on our Linux CI machines (Jenkins):

/home/builduser/.config/Cypress/cy/production/projects

I couldn't find any information about this. Are we doing something wrong causing these files to be generated?
Should Cypress automatically clear this? Do we have to run a certain command to clear them?

@cypress-bot cypress-bot bot added stage: backlog and removed stage: proposal 💡 No work has been done of this issue labels Apr 29, 2022
@cypress-app-bot
Copy link
Collaborator

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

@cypress-app-bot cypress-app-bot added the stale no activity on this issue for a long period label Jul 18, 2023
@cypress-app-bot
Copy link
Collaborator

This issue has been closed due to inactivity.

@cypress-app-bot cypress-app-bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2023
@gkrishna08
Copy link

@cypress-app-bot facing same issue while running the cypress on CI/Jenkins pipeline.. any update on this.
Thanks in advance

@jennifer-shehane
Copy link
Member

This is the Cypress App Data which is used to store things like preferences. It should be safe for you to delete everything in the cy folder if you want to add that into your automated process.

I know a lot of local state for cypress open is stored in there. I’m a little less sure of what the utility would be on a CI machine and whether we need to write data in that case.

What’s the size of the folders?

@jennifer-shehane jennifer-shehane added stage: needs investigating Someone from Cypress needs to look at this existing workaround prevent-stale mark an issue so it is ignored by stale[bot] and removed stale no activity on this issue for a long period labels Apr 12, 2024
@xuanvinhvu
Copy link

We're seeing this issue as well with our CI runs where our agent basically ran out of storage. The files are in /home/jenkins/.config/Cypress/cy/production/projects. Currently we're deleting the files using a cron job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
existing workaround prevent-stale mark an issue so it is ignored by stale[bot] stage: needs investigating Someone from Cypress needs to look at this
Projects
None yet
Development

No branches or pull requests

7 participants