Narrowing down regressions on trunk

Asa Sandahl asa.sandahl at linaro.org
Fri Jan 20 14:13:47 UTC 2012


Hi Michael,

Sure, I will put it up for next week.

Regards
Åsa

On 20 January 2012 01:49, Michael Hope <michael.hope at linaro.org> wrote:

> Hi Åsa.  The GCC 4.7 release is coming up and the ARM testsuite shows
> a lot of regressions:
>
> http://ex.seabright.co.nz/helpers/testlog/gcc-4.7~svn183205/logs/armv7l-natty-cbuild231-tcpanda03-cortexa9r1/gcc-testsuite.txt
>
> We've been running three builds a week:
>  http://ex.seabright.co.nz/helpers/buildlog/gcc-4.7~svn
>
> and can use the result to track down the range of commits where a
> fault was introduced or exposed.
>
> Could you please look through the results and narrow down where each
> failure appeared?  I've uploaded all of the results to:
>  http://people.linaro.org/~michaelh/incoming/trunks.tar.xz
>
> One way is to look at the testsuite-diff.txt in each build as it
> should show the change in test results between one build and the next
> but might be incomplete.  Another way is to pull the failures out of
> gcc-testsuite.txt and do a diff against the previous version.
>
> The output should be a revision range for each of the current failures.
>
> Script it up.  Don't do it by hand.  I'm not that mean.
>
> Ta,
>
> -- Michael
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linaro.org/pipermail/linaro-toolchain/attachments/20120120/3980721f/attachment.html>


More information about the linaro-toolchain mailing list