Launchpad itself

BinaryPackageBuildSet.getBuildsByArchIds orders inconsistently

Bug #604842 reported by William Grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

BinaryPackageBuildSet.getBuildsByArchIds orders by BuildQueue.lastscore DESC, BinaryPackageBuild.id, but Builder._findBuildCandidate orders by BuildQueue.lastscore DESC, BuildQueue.id. This means that retries will show up earlier in the visible build listings than their actual position in the queue (since their BuildQueue.id will be later).

Revision history for this message
Julian Edwards (julian-edwards) wrote :

What "visible build listings" do you mean?

Changed in soyuz:
status: New → Incomplete
Revision history for this message
William Grant (wgrant) wrote :

The distroseries build queue is the example that I saw. This morning, when filtered for NEEDSBUILD and ia64 (https://edge.launchpad.net/ubuntu/maverick/+builds?build_text=&build_state=pending&arch_tag=ia64), it was showing a whole lot of KDE builds at the head of the queue. They had been retried, so were in reality queued *behind* the rest.

Julian Edwards (julian-edwards)
Changed in soyuz:
status: Incomplete → Triaged
importance: Undecided → Low
tags: added: soyuz-build
Julian Edwards (julian-edwards)
tags: added: trivial
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.