You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that cannot be changed using a configuration option.
In my current situation a single run creates 12Gb of data and it is growing as we add more tests. It would be nice if there was a way to change this number. I'd sacrifice the debug-ability to save disk-space. At least till we can find other ways to reduce the disk usage. Others might want to keep more history.
The text was updated successfully, but these errors were encountered:
szabgab
changed the title
Allow changing the number temporary directories pytests keeps which is currently 3
Allow changing the number temporary directories pytest keeps which is currently 3
Feb 3, 2022
Thanks. That solves the problem for me. Maybe the documentation could be amended with :
"The number of entries currently cannot be changed, but using the --basetemp option will remove the directory before every run effectively meaning the tempfiles of only the most recent run will be kept."
"The number of entries currently cannot be changed, but using the --basetemp option will remove the directory before every run effectively meaning the tempfiles of only the most recent run will be kept."
Sounds good, would you like to contribute that to the docs?
Currently
pytest
will keep the last 3 root temporary directories for each testing session, for all tests.As far as I can tell it is a hard-coded parameter here:
pytest/src/_pytest/tmpdir.py
Line 148 in a53abe9
that cannot be changed using a configuration option.
In my current situation a single run creates 12Gb of data and it is growing as we add more tests. It would be nice if there was a way to change this number. I'd sacrifice the debug-ability to save disk-space. At least till we can find other ways to reduce the disk usage. Others might want to keep more history.
This is related to #8141 as well.
The text was updated successfully, but these errors were encountered: