This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: RFC: KFAIL DejaGnu patch
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: eliz at is dot elta dot co dot il, rob at welcomehome dot org, ac131313 at cygnus dot com,fnasser at redhat dot com, gdb-patches at sources dot redhat dot com
- Date: Mon, 8 Apr 2002 14:37:57 -0400
- Subject: Re: RFC: KFAIL DejaGnu patch
- References: <200204081733.g38HXsf03252@duracef.shout.net>
On Mon, Apr 08, 2002 at 12:33:54PM -0500, Michael Elizabeth Chastain wrote:
> Rob Savoye writes:
> > btw - Matt says he'll add the extra fields for ERROR and WARNING to the
> > XML output, which he's hoping will be done as soon as he firms up the DTD.
> > Anything else you need to have that be useful ?
>
> Now there is an open ended question. I'll ramble on it for a while.
>
> ERRORs and WARNINGs: it would help if all ERRORs and WARNINGs went
> through report_test and got treated like the other results, including
> printing the name of the current test script. Right now I pick this up
> when I am lexing the gdb.sum file.
>
> Duplicate test names: we have as many as 30 tests in the same file
> with the same name (often named "continue"). Right now I add sequence
> numbers to this when I am lexing the gdb.sum file:
>
> gdb.base/foo.exp: continue
> gdb.base/foo.exp: continue {2}
> gdb.base/foo.exp: continue {3}
>
> It would be nice if DejaGnu did this automatically.
That would only be useful if we always marked all tests - which we're
awful about. continue {2} might be any number of different continue
statements in the test.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer