From: David Carlton <carlton@kealia.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [testsuite] add gdb.cp/gdb1355.exp
Date: Thu, 18 Sep 2003 00:48:00 -0000 [thread overview]
Message-ID: <yf2d6dyexbi.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <200309180000.h8I00rK4012420@duracef.shout.net> (Michael Elizabeth Chastain's message of "Wed, 17 Sep 2003 20:00:53 -0400")
On Wed, 17 Sep 2003 20:00:53 -0400, Michael Elizabeth Chastain <mec@shout.net> said:
> If you use a version of gcc with this bug, plenty of other
> things break, so this test does not add any coverage.
> It does add an explicit KFAIL that points to the specific PR.
I don't think this matches our use of KFAIL. For one thing, it would
be an XFAIL, because it's a GCC bug, not a GDB bug. For another
thing, though, the bug in question has been fixed, so we don't expect
it to fail: if it does, it should show up as a FAIL. I would leave in
the new test, with branches and comments as is, but I would change all
the occurrences of kfail to fail.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-09-18 0:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 0:00 Michael Elizabeth Chastain
2003-09-18 0:48 ` David Carlton [this message]
2003-09-18 0:54 Michael Elizabeth Chastain
2003-09-18 0:56 ` Daniel Jacobowitz
2003-09-18 1:20 ` David Carlton
2003-09-18 1:27 ` David Carlton
2003-09-18 2:01 Michael Elizabeth Chastain
2003-09-18 14:27 ` Andrew Cagney
2003-09-18 16:05 ` David Carlton
2003-09-18 15:38 ` David Carlton
2003-09-18 15:33 Michael Elizabeth Chastain
2003-09-20 21:40 ` Andrew Cagney
2003-09-18 21:22 Michael Elizabeth Chastain
2003-09-18 21:27 Michael Elizabeth Chastain
2003-09-20 21:46 ` Andrew Cagney
2003-09-20 22:31 ` Daniel Jacobowitz
2003-09-21 0:51 ` Andrew Cagney
2003-09-20 21:59 Michael Elizabeth Chastain
2003-09-20 22:03 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=yf2d6dyexbi.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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