[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Sparc build failure analysis (was Re: StrongARM tactics)

On Sun, Dec 11, 2005 at 05:30:24AM -0500, Kevin Mark wrote:

> has anyone every considered a check in the buildd infrastructure to
> alert someone (buildd admin and/or others) if a build is taking too long
> (eg openoffice usually takes between 2-3 hours to build and the current
> build has been building for 10 hours+). Something like a database entry
> or a database of either previous build times or last build time. As a
> way to not have a buildd tied up with an obvious build issue and thus
> allow the issue to be address sooner thus alowing more buildd
> throughput.

You mean something like the stats on http://www.buildd.net/ - for example:

I intend to give some sort of "build is overdue" warning when I have enough
data to calculate on when a build is overdue.... ;)

Ciao...                //        Fon: 0381-2744150 
      Ingo           \X/         SIP: 2744150@sipgate.de

gpg pubkey: http://www.juergensmann.de/ij/public_key.asc

Attachment: signature.asc
Description: Digital signature

Reply to: