On Mar 12, 2012, at 11:59 AM, Diego Novillo wrote:
> On 12/03/12 14:58 , Doug Kwan wrote:
>
>> 2012-03-12 Doug Kwan<dougk...@google.com>
>>
>> * contrib/testsuite-management/arm-grtev2-linux-gnueabi.xfail:
>> New file.
>
> OK.
Hum, kinda makes be wish we had all the xfail files for the release branches
and trunk for all primary and secondary platforms and that make check did
something more intelligent. :-) One advantage, people doing day to day work,
would rarely have to do two make check runs, as they could do just one and do
the analysis against the checked in file. They would only have to do two, if
the file isn't up-to-date.
So, I guess the question is, is there a down side to doing that? I can imagine
a
if [ -r "$srcdir/contrib/testsuite-management/$target.xfail ]; then
$srcdir/contrib/testsuite-management/validate_failures.py bla
bla
fi
added into make check somewhere.
