From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2301 invoked by alias); 3 Feb 2004 00:23:54 -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 2294 invoked from network); 3 Feb 2004 00:23:53 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 3 Feb 2004 00:23:53 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AnoM4-000499-DU; Mon, 02 Feb 2004 19:23:52 -0500 Date: Tue, 03 Feb 2004 00:23:00 -0000 From: Daniel Jacobowitz To: Fred Fish Cc: gdb-patches@sources.redhat.com Subject: Re: [RFC] Framework for selectively omitting individual testsuite tests or directories for local use only Message-ID: <20040203002351.GA393@nevyn.them.org> Mail-Followup-To: Fred Fish , gdb-patches@sources.redhat.com References: <200402021713.43140.fnf@ninemoons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402021713.43140.fnf@ninemoons.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-02/txt/msg00049.txt.bz2 On Mon, Feb 02, 2004 at 05:13:43PM -0700, Fred Fish wrote: > Very often when I'm working with a gdb that has very poor testsuite > results, I want to set things up so that I can selectively omit > individual troublesome tests or even entire directories of tests. > > That way the I can get a completely clean gdb testsuite run, and then > start tackling the troublesome tests one a time, without having to > filter out the hundreds of other failures I haven't yet gotten around > to fixing. Also, a clean testsuite runs *MUCH* faster than one that > has hundreds of timeouts or other such issues. For example, the > current sh-elf gdb seems to hang forever if you don't avoid running > the gdbtk tests. > > Dejagnu supports "ignoretests" and "ignoredirs" lists of specific > individual tests or directories to ignore. Below is a patch that I > frequently apply locally to any gdb tree I'm working on. > > I'd like to propose that we add it, or something like it, to the > testsuite strictly for use as a debugging aid. It's not intended to > become a permanent way for various configurations to hide their more > problematic test cases, just a framework for developers to use > locally. > > Comments? To be honest, I don't see the point of adding this. Take a look at what your change does: > *************** site.exp: ./config.status Makefile > *** 111,116 **** > --- 114,121 ---- > @echo "set build_triplet ${build_canonical}" >> ./tmp0 > @echo "set srcdir ${srcdir}" >> ./tmp0 > @echo "set tool gdb" >> ./tmp0 > + @echo "lappend ignoredirs ${ignoredirs}" >>./tmp0 > + @echo "lappend ignoretests ${ignoretests}" >>./tmp0 > @echo "## All variables above are generated by configure. Do Not Edit ##" >> ./tmp0 > @cat ./tmp0 > site.exp > @cat site.bak | sed \ OK... there is a much easier way. drow@nevyn:~% echo $DEJAGNU /home/drow/.dejagnu/site.exp drow@nevyn:~% cat >> $DEJAGNU <