Hi Diego
This patch adds arm-grtev2-linux-gnueabi.xfail for our 4.6 branch
so that we can track regressions. This just established the test
baseline. The failures need to be investigated.
-Doug
2012-03-12 Doug Kwan dougk...@google.com
*
On 12/03/12 14:58 , Doug Kwan wrote:
2012-03-12 Doug Kwandougk...@google.com
* contrib/testsuite-management/arm-grtev2-linux-gnueabi.xfail:
New file.
OK.
Diego.
On Mar 12, 2012, at 11:59 AM, Diego Novillo wrote:
On 12/03/12 14:58 , Doug Kwan wrote:
2012-03-12 Doug Kwandougk...@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
On 12/03/12 15:27 , Mike Stump wrote:
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
On Mar 12, 2012, at 12:37 PM, Diego Novillo wrote:
Ideally, though, we would not even need this hack. 'make check' should
return 0 when every test is nominal. Period.
Yeah, that pig has yet to achieve lift-off. :-)
On 12 March 2012 18:58, Doug Kwan dougk...@google.com wrote:
Hi Diego
This patch adds arm-grtev2-linux-gnueabi.xfail for our 4.6 branch
so that we can track regressions. This just established the test
baseline. The failures need to be investigated.
Just out of
Hi Ramana,
We know the limit of the QEMU and already noticed failure due to
the simulator. Like I said, this is used as the baseline. We are
going to look at the failures carefully to categorize them. We
noticed that some tests fail randomly on QEMU, these are marked as
flaky and the
