[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 02:38:35PM +0100, Jeroen van Wolffelaar wrote:
> On Sun, Dec 11, 2005 at 12:35:26AM -0800, Steve Langasek wrote:
> > On Sat, Dec 10, 2005 at 06:53:47AM -0800, Blars Blarson wrote:
> > > FAILED

> > But FAILED is an advisory state anyway; it doesn't directly benefit the
> > port, at all, to have the package listed as "Failed", this is just a
> > convenience for folks sifting through the build failures (like the rarely
> > used "confirmed" BTS tag is for maintainers).  In the long-term, one of two
> > things needs to happen with each of these build failures: the package needs
> > to be added to P-a-s so the arch no longer tries to build it, or the package
> > needs to be fixed -- via porter NMU if necessary.

> > So as you have the list of these packages, as a porter you can proceed with
> > figuring out which of the two categories each falls into, and take the
> > necessary action without worrying about the "Failed" state, yes?

> Indeed, for practical buildd maintainance purposes, the distinction is
> not that important -- though 'Failed' is known to not benefit of a
> requeue, while 'Building:Maybe-Failed' might or might not, it's unkown,
> most archs should have enough surplus buildd power that retrying
> everything once in a while doesn't hurt.

> The major benefit is though to make it apparant for porters what to look
> into, without all the 'noise' in between of maybe-transient failures.
> One could also make sure that the FTBFS bugs are tagged (user-tagged)
> with debian-sparc@l.d.o (etc) for example (or $arch@buildd.d.o? There
> doesn't exist a d-mipsel@l.d.o for example...), so that one can get a
> nice overview of all the porting bugs. It'd make sense to synchronise
> this across all architectures, so that it is consistent.


Our porters can beat up your porters.


Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply to: