From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24938 invoked by alias); 8 Apr 2002 17:34:49 -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 24924 invoked from network); 8 Apr 2002 17:34:47 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 8 Apr 2002 17:34:47 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id g38HXsf03252; Mon, 8 Apr 2002 12:33:54 -0500 Date: Mon, 08 Apr 2002 10:34:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200204081733.g38HXsf03252@duracef.shout.net> To: eliz@is.elta.co.il, rob@welcomehome.org Subject: Re: RFC: KFAIL DejaGnu patch Cc: ac131313@cygnus.com, drow@mvista.com, fnasser@redhat.com, gdb-patches@sources.redhat.com X-SW-Source: 2002-04/txt/msg00310.txt.bz2 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. 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. 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. Clean up the bug id stuff: the name "PRMS" is hard wired into Dejagnu! I also have a lot of vague stuff related to scaling up the testing process. Right now I run 30 configurations per week. I use external scripts to manage my archive of test results. I don't want dejagnu to be in the business of managing 100's of test scripts, but eventually I will want some 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). All of this stuff is just me; the gdb group hasn't talked this over and reached any kind of consensus yet. Michael C