Launchpad itself

Why are my packages stuck in the build queue?

Asked by David Huggins-Daines

My packages:

https://launchpad.net/~dhuggins/+archive/cmusphinx/+builds?build_state=pending

Have been pending for the last 5 hours, perpetually "building in 3 hours". It doesn't look like the build farm is particularly busy:

https://launchpad.net/builders

In particular there are a couple of i386 and lpia machines available.

Is there something wrong with my packages or the queue?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
David Huggins-Daines (dhuggins) said : 		#1

Now eight hours old and they're still scheduled to build "in 3 hours".

Revision history for this message
Julian Edwards (julian-edwards) said : 		#2

(I see your builds have completed now)

The build farm is very busy at the moment because of the upcoming release - there's a rebuild happening which, although is at the lowest priority, will block builders a bit more than normal.

On top of that, there's a scalability bug in the dispatching process which means that builders can sit idle for 20 minutes while completed builds are being collected from the other builders. This will get fixed in due course.

Also, there's a "fairness" aspect to the scheduling which prevents any one PPA from hogging all the builders of a particular architecture. This can cause confusion when builders appear idle but there's a large queue of builds waiting.

Finally, the estimated dispatch time is an "estimate" - it's very hard to get precisely right and the margin of error increases dramatically the further down the queue the build is.

Hope that helps explain the situation.

Can you help with this problem?

Provide an answer of your own, or ask David Huggins-Daines for more information if necessary.

To post a message you must log in.