Launchpad itself

Jobs restarted?

Asked by Jack Radigan

I had two kernel builds running for nearly 5 hours and they've both been recently restarted without any indication or email as to why:

https://launchpad.net/~centrych-dev/+archive/kernel/+build/5886486
https://launchpad.net/~centrych-dev/+archive/kernel/+build/5886487

I understand that Launchpad's a free service and I'm grateful it's available.

Just the same, whacking someone's builds 5 hours after they started is a bit much, especially without so much as an email.

Thanks,

-jack-

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Jack Radigan
Solved:
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said : 		#1

PPAs don't have any build time guarantees, and builds can be restarted at any time. Much of our build hardware is on temporary loan from other services, so we can make use of their capacity when they don't need it and they can take it back when they do, causing builds to be restarted on remaining hardware. Sometimes a builder host has some kind of failure or needs maintenance, also causing its builds to be reset. This is a normal part of the system that has very minimal impact on the vast majority of users, so we don't spam people with emails saying that their build has been delayed for a short period.

A delay of five hours is perhaps more inconvenient, but it's also not uncommon for builds to queue for multiple hours when our service is under heavy load, and it would be extremely spammy to email everyone in that situation. Builds on a shared service will occasionally take an unpredictable length of time, and there's not much that can be done about that.

Revision history for this message
Jack Radigan (jprad) said : 		#2

Hmm, I guess my initial post was too subtle...