From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20537 invoked by alias); 9 Apr 2002 14:50:45 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 20530 invoked from network); 9 Apr 2002 14:50:44 -0000 Received: from unknown (HELO darkstar.welcomehome.org) (192.203.188.2) by sources.redhat.com with SMTP; 9 Apr 2002 14:50:44 -0000 Received: (from rob@localhost) by darkstar.welcomehome.org (8.11.3/8.11.3) id g39Ewgw12164; Tue, 9 Apr 2002 08:58:42 -0600 Date: Tue, 09 Apr 2002 07:50:00 -0000 From: Rob Savoye To: Michael Elizabeth Chastain Cc: eliz@is.elta.co.il, rob@welcomehome.org, ac131313@cygnus.com, drow@mvista.com, fnasser@redhat.com, gdb-patches@sources.redhat.com Subject: Re: RFC: KFAIL DejaGnu patch Message-ID: <20020409085842.B11086@welcomehome.org> References: <200204081733.g38HXsf03252@duracef.shout.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200204081733.g38HXsf03252@duracef.shout.net>; from Michael Elizabeth Chastain on Mon, Apr 08, 2002 at 12:33:54PM -0500 X-SW-Source: 2002-04/txt/msg00358.txt.bz2 On Mon, Apr 08, 2002 at 12:33:54PM -0500, Michael Elizabeth Chastain wrote: > Now there is an open ended question. I'll ramble on it for a while. Really, I might have stepped in a deep one there... :-) I was thinking of changes the XML format, but these are mostly good suggestions. > 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. This is probably a good idea. > 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: > It would be nice if DejaGnu did this automatically. Um, I don't think it's the responsibility of DejaGnu to work around a poor programming practice. > TIMEOUT: I would like to have a new test result of TIMEOUT for a test > that times out. A TIMEOUT often indicates that gdb has crashed, and is > much more serious than an ordinary FAIL. If GDB has crashed, this is supposed to be UNRESOLVED, according to POSIX. UNRESOLVED is a test case that can't be finished, and needs a human to look at it. UNTESTED is when there isn't support in the underlying OS or hardware to run a test case. > Split gdb.log file: when I look at gdb.log, I am usually interested in > just one test script. So I'd like to have a directory of gdb.log files, > one per each test script. I don't need the giant log. Hum... I might try that. Mind you, the log files were more for debugging purposes, than analysing them for test results. > features to add more stuff to the log file (like a uuid, the email > address of the person who ran the test, the version of binutils and > gcc used when testing gdb, and lots of stuff like that). Most of this is GDB testing specific, but I'll see what I can do. I can probably add an "output_hook", that lets test suites add their own info to the log. > All of this stuff is just me; the gdb group hasn't talked this over > and reached any kind of consensus yet. Any changes I make have to work generically, since the gdb team is a only part of the DejaGnu user community. - rob -