code imports are not cleaned up on disk after an import times out

Bug #497569 reported by Michael Hudson-Doyle
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad code imports
Triaged
Low
Unassigned

Bug Description

Because the worker script itself is responsible for removing its scratch directory, if it's killed sufficiently hard (i.e. with SIGKILL not SIGINT) the scratch directory sits around on disk. This probably isn't ideal.

tags: added: code-import
Tim Penhey (thumper)
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Low
Colin Watson (cjwatson)
affects: launchpad → lp-codeimport
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.