build directory is fixed and not cleaned up on SIGTERM
Bug #319247 reported by
James Troup
This bug report is a duplicate of:
Bug #32236: Launchpad Buildd doesn't clean up old respective build dir.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| launchpad-buildd |
Triaged
|
High
|
Unassigned | ||
Bug Description
If shutdown by SIGTERM (e.g. because of an upgrade of the launchpad-buildd package, or shutdown), the buildd won't clean up the build directory. This causes the buildd to explode when the package is retried on the same machine. It'd probably be a good idea for the buildd to have a SIGTERM handler that invokes the normal end-of-build clean up stuff, at least in terms of what's on disk.
| Changed in launchpad-buildd: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| Changed in launchpad-buildd: | |
| importance: | Medium → High |
| summary: |
- should have a sigterm handler + build directory not cleaned up on SIGTERM |
| summary: |
- build directory not cleaned up on SIGTERM + build directory is fixed and not cleaned up on SIGTERM |
Revision history for this message
| Robert Collins (lifeless) wrote | #2 |
To post a comment you must log in.
Or we could use a temp dir that doesn't need cleanup.