-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
4000+ tests eats up disk space *nom* #4160
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug/issue
Hi! Here's something I've noticed:
Every time a test starts up, Chrome creates two folders under
/tmp/
:/tmp/.com.google.Chrome.PyT0E2
(empty)/tmp/.org.chromium.Chromium.OBIvvs
(aprox 9 megabytes)Though both folders are left behind when the test shuts down, which eventually eats up all my disk space when running 4000+ tests (4000 * 9mb = 36GB).
This doesn't happen on Nightwatch v1.7.11, (I've just been upgrading).
Steps to reproduce
npm init nightwatch
(from https://nightwatchjs.org/guide/quickstarts/create-and-run-a-nightwatch-test.html)/tmp/
folder.npx nightwatch ./nightwatch/examples/basic/ecosia.js
npx nightwatch ./nightwatch/examples
/tmp/
folder as Chrome creates folders and leaves them behind.Sample test
No response
Command to run
No response
Verbose Output
No response
Nightwatch Configuration
No response
Nightwatch.js Version
3.5.0
Node Version
20.5.1
Browser
Chrome 123.0.6312.86 (Official Build) (64-bit)
Operating System
Ubuntu 20.04.6 LTS
Additional Information
No response
The text was updated successfully, but these errors were encountered: