From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu, drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] KFAIL gdb.c++/annota2.exp watch triggered on a.x
Date: Fri, 03 Jan 2003 22:12:00 -0000 [thread overview]
Message-ID: <200301032212.h03MCQa20253@duracef.shout.net> (raw)
One advantage of David's code is that when the bug gets fixed,
people see a more informative message for a while: "KPASS gdb/38"
rather than "PASS".
One disadvantage is that it adds more file editing steps to the
lifecycle. David, what edits, exactly, are you envisioning
when "KPASS gdb/38" starts popping up?
You shouldn't delete this part:
-re "known bad expression" {
kfail "gdb/NNN" "test name"
}
... because old bugs have a way of popping up again, especially
when additional configurations get tested.
Michael C
next reply other threads:[~2003-01-03 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 22:12 Michael Elizabeth Chastain [this message]
2003-01-03 22:27 ` David Carlton
-- strict thread matches above, loose matches on Subject: below --
2003-01-03 23:19 Michael Elizabeth Chastain
2003-01-03 21:36 David Carlton
2003-01-03 21:39 ` Daniel Jacobowitz
2003-01-03 21:48 ` David Carlton
2003-01-03 21:51 ` Daniel Jacobowitz
2003-01-03 22:14 ` David Carlton
2003-01-03 22:30 ` Daniel Jacobowitz
2003-01-03 22:57 ` David Carlton
2003-01-09 17:10 ` David Carlton
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=200301032212.h03MCQa20253@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.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