conda-build writing to /tmp directory and not cleaning up #4847
Labels
source::community
catch-all for issues filed by community members
stale::recovered
[bot] recovered after being marked as stale
type::bug
describes erroneous operation, use severity::* to classify the type
Checklist
What happened?
I think this is the same issue as reported here: #2289 (that one is closed, so I don't know if it's OK to add a new one, but not sure what else to do). It's a serious bug that hasn't been fixed.
When I run
conda-build
on Linux (in a CI) I end up with a/tmp/tmpxxxxxxx
directory with the entire contents on my package (in my case up to a GB), which conda-build isn't cleaning up. So over the course of a day, I might end up with 20 GB of files there.It seems as if the only open issue related to this is here?: conda/conda#6631
Is there any way to know what the tmp directory is that conda-build is creating, so I can try to manually delete it at the end of the job? I can't just delete all of them because I don't want to delete them from other jobs that may still be running.
Using
conda-build=3.23.3
,conda=23.1.0
. On a Linux machine.Conda Info
Conda Config
No response
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: