From: Daniel Jacobowitz <drow@mvista.com>
To: Fred Fish <fnf@ninemoons.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Framework for selectively omitting individual testsuite tests or directories for local use only
Date: Tue, 03 Feb 2004 00:23:00 -0000 [thread overview]
Message-ID: <20040203002351.GA393@nevyn.them.org> (raw)
In-Reply-To: <200402021713.43140.fnf@ninemoons.com>
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 <<EOF
if { "$tool" == "gdb" } {
lappend ignoredirs gdb.cp
}
EOF
$target_alias is there too. Even $srcdir should be available by this
point, giving you great freedom.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-03 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 0:13 Fred Fish
2004-02-03 0:23 ` Daniel Jacobowitz [this message]
2004-02-03 0:24 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040203002351.GA393@nevyn.them.org \
--to=drow@mvista.com \
--cc=fnf@ninemoons.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox