From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com,
Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: [patch/rfc] KFAIL gdb.c++/annota2.exp watch triggered on a.x
Date: Fri, 03 Jan 2003 22:57:00 -0000 [thread overview]
Message-ID: <ro14r8plu3t.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030103223031.GA15995@nevyn.them.org>
On Fri, 3 Jan 2003 17:30:31 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> How about a compromise: we agree not to remove kfail patterns in the
> testsuite, but instead replace them with specific fail patterns and
> a commented out reference to the failure. That makes life much
> simpler.
That sounds to me like the best of both worlds: we get the output that
I want, while making it as easy as possible to stick the KFAILs back
in the test suite if the same bug crops up again.
> I still don't see what the point of the KPASS's is.
Honestly, there isn't much of a point to them. They serve as a
reminder to get rid of KFAILs once you've fixed a bug (because KPASSes
will show up in the output of 'runtest' or 'make check'), and they
might be useful if you're interested in tracking down exactly under
what conditions a bug manifests itself. But I don't feel strongly
about either of those issues; if nobody likes KPASS but me, then I
have no objection to using plain old PASS instead.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-01-03 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-01-09 17:10 ` David Carlton
2003-01-03 22:12 Michael Elizabeth Chastain
2003-01-03 22:27 ` David Carlton
2003-01-03 23:19 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=ro14r8plu3t.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.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