linaro-infrastructure-stakeholders team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxx>]

On Thu, Jan 20, 2011 at 03:21:25PM -0500, James Westby wrote:
> On Tue, 11 Jan 2011 09:19:50 -0600, Steve Langasek <steve.langasek@xxxxxxxxxx> wrote:
> > The Developer Platform team has need for a tool to facilitate mass
> > bugfilings for package build failures on ARM.  Requirements:

> >  - process the output of periodic rebuilds (e.g.
> >    http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110107-natty.html)
> >    to identify build failures that are specific to armel (obviously this
> >    requires an armel rebuild as input... the above example rebuild is
> >    not)

> We are only interested in rebuild tests at this time?

Yes.

> >  - tag resulting bugs with 'ftbfs' tag and an 'arm-porting-queue' tag
> >  - avoid filing new bugs on a package when there is an existing open bug on
> >    that package with these tags
> >  - script must be runnable from the commandline / cron

> > Nice-to-have features:

> >  - recognizing when a build failure is not a regression from the last time
> >    the script was run, to avoid filing a new bug report (since a build
> >    failure may be a bug in a *different* package, and have been reassigned
> >    to a different package as part of triage)

> Good point.

> >  - allow filing 'ftbfs' bug reports for non-armel build failures

> > This is a prerequisite for having an effective porting queue for handling
> > ARM package build failures.

> I believe this team is supposed to be up and running this cycle?

That is the goal.  If it's not possible to get tools in place to support
this in that time frame, we'll muddle through with the existing 'armel'
tagged bug list, but that will be much less effective.

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

Attachment: signature.asc
Description: Digital signature