This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [testsuite] Skip gcc.c-torture/execute/960321-1.c on Solaris 2/x64 with Sun as
- From: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- To: Ben Elliston <bje at air dot net dot au>
- Cc: Jason Merrill <jason at redhat dot com>, gcc-patches at gcc dot gnu dot org, Janis Johnson <janis dot marie dot johnson at gmail dot com>
- Date: Thu, 10 Jun 2010 13:09:03 +0200
- Subject: Re: [testsuite] Skip gcc.c-torture/execute/960321-1.c on Solaris 2/x64 with Sun as
- References: <yddeihrkhnh.fsf@manam.CeBiTec.Uni-Bielefeld.DE> <4BF6AB35.1090707@redhat.com> <yddd3wpqlnh.fsf@manam.CeBiTec.Uni-Bielefeld.DE> <4BF6D24F.2010800@redhat.com> <yddpr02d5r9.fsf@manam.CeBiTec.Uni-Bielefeld.DE> <20100610104335.GA14767@air.net.au>
Ben Elliston <bje@air.net.au> writes:
> On Mon, Jun 07, 2010 at 09:03:54PM +0200, Rainer Orth wrote:
>
>> While this seems to make sense if I read the DejaGnu manual
>> describing that test outcome, it doesn't seem to take into account
>> XFAIL: after an XFAILed compilation test, it is completely expected
>> that the corresponding execution test fails, too. Having this in
>> mail-report.log is just useless noise.
>
> This is the long established tradition for DejaGnu tests. I think it
> makes sense (more or less) and shouldn't be changed. I would suggest
> filtering them, using a specific filter expression (ie. don't filter
> all UNRESOLVED results).
Indeed: I was worried about omitting all UNRESOLVED results in
test_summary output, since they could have other reasons worth
noticing. I'll check how to do this in test_summary.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University