tarmac doesn't clean up /tmp usage correctly
Bug #1099438 reported by
Andreas Hasenack
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Tarmac |
Confirmed
|
High
|
dobey | ||
Bug Description
We got into a situation where /tmp was using up 3.6Gb. It was full of temporary directories created by tarmac as bzr branches.
Looking at the code, it only tries to remove the temporary directory in __del__() method in the Branch class:
def __del__(self):
"""Do some potenetially necessary cleanup during deletion."""
if self.temp_tree_dir is not None:
Apparently that does not always run.
| Changed in tarmac: | |
| importance: | Undecided → High |
| assignee: | nobody → Rodney Dawes (dobey) |
| status: | New → Confirmed |
Revision history for this message
| dobey (dobey) wrote | #1 |
| tags: | added: landscape |
| tags: | removed: landscape |
To post a comment you must log in.
For posterity, when running tarmac to land tarmac branches, the following occurs during tearDown of some of the tests:
Exception OSError: OSError(2, 'No such file or directory') in <bound method Branch.__del__ of <tarmac.
The tests pass and it appears __del__ is being called, albeit inconsistently. It's also still unclear why it wouldn't be called in normal usage, even in the worst case of when the python interpreter cleans up and exits.