Launchpad itself

Builds stuck in manual-depwait state should eventually give up and fail

Bug #191701 reported by Martin Pool
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

https://edge.launchpad.net/~bzr/+archive/+build/497787

still in Pending mode after a month. I think this ftbfs, so why isn't it just failed?

Martin Pool (mbp)
Changed in launchpad:
assignee: nobody → cprov
Celso Providelo (cprov)
Changed in soyuz:
milestone: none → 1.2.3
status: New → Triaged
Revision history for this message
Celso Providelo (cprov) wrote :

For the record, I've increased its priority (was 1020) and it got processed, dep-wait on 'python-central' which doesn't exist in dapper. I will investigate why they got stuck for such a long time in queue.

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 191701] Re: build stuck in pending state

This particular build as you say is probably stuck waiting for
dependencies. But I would think after nearly a month you might as
well give up?

--
Martin

Revision history for this message
Martin Pool (mbp) wrote : Re: build stuck in pending state

I don't think this is a duplicate. Rather, this is a report that for PPAs, after say one week in build-dep, the build should be considered failed.

Celso Providelo (cprov)
Changed in soyuz:
milestone: 1.2.3 → 1.2.4
Julian Edwards (julian-edwards)
Changed in soyuz:
milestone: 1.2.4 → none
Celso Providelo (cprov)
Changed in soyuz:
status: Triaged → New
Celso Providelo (cprov)
summary: - build stuck in pending state
+ Build stuck in manual-depwait state
Julian Edwards (julian-edwards)
summary: - Build stuck in manual-depwait state
+ Builds stuck in manual-depwait state should eventually give up and fail
Changed in soyuz:
status: New → Triaged
importance: Undecided → Low
assignee: Celso Providelo (cprov) → nobody
Revision history for this message
Colin Watson (cjwatson) wrote :

I would not be in favour of failing such builds. It's common enough in Ubuntu for something to be auto-synced prematurely which is just waiting for one of its build-dependencies to get through Debian NEW so that we can have it, or perhaps to be waiting for an Ubuntu developer to perform a merge. It's actively helpful for builds to stay in dep-wait so that they're easy to find, and it does no harm; in fact it's better categorisation than failed, which could be almost anything. I don't really see why the situation is much different for PPAs: dep-wait does no harm and is a clearer categorisation.

To be honest, I'd prefer this bug to be Won't Fix.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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