Some builds fail when they should depwait
Bug #160439 reported by
William Grant
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpad-buildd |
Triaged
|
Low
|
Unassigned |
Bug Description
The buildds apparently fail to detect missing dependencies in some situations, and throw builds to FAILED instead of MANUALDEPWAIT. I've only seen it happen when one of the dependencies fails to install because of missing dependencies. I presume there isn't code to check failures to satisfy child build dependencies.
This shouldn't cause it to go to FAILED, as that requires manual retrying. MANUALDEPWAIT is appropriate, although I doubt it will be easy to work out which dependency is missing.
Changed in soyuz: | |
assignee: | nobody → cprov |
importance: | Undecided → Medium |
Changed in soyuz: | |
milestone: | 1.1.12 → 1.2.1 |
Changed in soyuz: | |
assignee: | cprov → adconrad |
milestone: | 1.2.1 → none |
Changed in launchpad-buildd: | |
assignee: | Adam Conrad (adconrad) → nobody |
tags: | added: sbuild |
Changed in launchpad-buildd: | |
importance: | Medium → Low |
To post a comment you must log in.
We will work on the buildd code soon, let's keep it as 'triaged' for the next milestone.