linaro-infrastructure-stakeholders team mailing list archive

[James Westby <james.westby@xxxxxxxxxxxxx>]

On Tue, 11 Jan 2011 09:19:50 -0600, Steve Langasek <steve.langasek@xxxxxxxxxx> wrote:
> Hi there,

Hi Steve,

> 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?

>  - 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?

Thanks,

James