From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: Clean up gdb.c++ tests for dwarf 1
Date: Wed, 05 Feb 2003 21:43:00 -0000 [thread overview]
Message-ID: <20030205214316.GA27592@nevyn.them.org> (raw)
In-Reply-To: <vt2of5qquvp.fsf@zenia.red-bean.com>
On Wed, Feb 05, 2003 at 04:29:14PM -0500, Jim Blandy wrote:
>
> Michael Elizabeth Chastain <mec@shout.net> writes:
> > gdb HEAD%20030205 has loads of this stuff in the C++ test suite:
> >
> > setup_xfail_format "DWARF 1"
> >
> > There are 81 instances of this.
> >
> > Some test scripts have them, and some don't. I'd like to get rid
> > of them and replace them with something more coherent -- or nothing.
> >
> > I see four choices.
> >
> > (1) Just remove these calls to setup_xfail_format. If someone runs the
> > gdb test suite with DWARF 1, the test suite will do its job and give
> > FAIL results for all the C++ tests that do not work with DWARF 1.
>
> Your rationale here is that, since we don't really know which of these
> failures are genuine, can't-be-done-with-Dwarf-1 expected failures,
> and which are GDB bugs, you want to dump them all into the "genuine
> bug" category and start re-categorizing, using our modern
> interpretation of XFAIL and KFAIL?
I think his rationale here is, we don't know which of these failures
are which, and we don't care...
I certainly don't care either. I like (1).
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-05 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 21:30 Michael Elizabeth Chastain
2003-02-05 21:37 ` David Carlton
2003-02-05 21:38 ` Jim Blandy
2003-02-05 21:43 ` Daniel Jacobowitz [this message]
2003-02-05 22:06 ` David Carlton
2003-02-05 22:18 ` Elena Zannoni
2003-02-05 22:41 Michael Elizabeth Chastain
2003-02-05 22:45 Michael Elizabeth Chastain
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=20030205214316.GA27592@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@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