This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: Testing for runtime errors
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: Jerry DeLisle <jvdelisle at verizon dot net>
- Cc: Fortran List <fortran at gcc dot gnu dot org>, janis187 at us dot ibm dot com
- Date: Fri, 28 Apr 2006 10:37:33 -0700
- Subject: Re: Testing for runtime errors
- References: <44519C4B.6020601@verizon.net>
On Thu, Apr 27, 2006 at 09:38:35PM -0700, Jerry DeLisle wrote:
> (Andrew Pinski suggested I cc Janis on this)
>
> Do you have any suggestions on how to test for run time error messages in
> the gfortran testsuite? When there is a runtime error, the test program
> exits with "1" so the dejagnu magic interprets it as a failure.
There are lots of possibilities for new DejaGnu magic if what you want
doesn't currently exist.
> I don't want an XFAIL because that usually means its expected to fail until
> it gets fixed.
>
> It would be useful to have the test machinery accept a non-zero exit in
> some cases and then use dg-output to check that the error message occurred
> as expected.
Not just useful, but necessary if that's what's needed to test parts of
your language support.
> I may have just stated a conflicting goal, but this has come up before and
> I thought I would query for a solution one more time.
I'll take a look next week. Ping me if you don't hear anything.
Janis