From: David Carlton <carlton@math.stanford.edu>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: RFC: gdb.c++/main-falloff.exp (a new KFAIL)
Date: Fri, 03 Jan 2003 21:24:00 -0000 [thread overview]
Message-ID: <ro1u1gqkjux.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <200301032116.h03LGhq19408@duracef.shout.net>
On Fri, 3 Jan 2003 15:16:43 -0600, Michael Elizabeth Chastain <mec@shout.net> said:
> I'm changing my mind about the gdb_test_multiple approach. I'm not
> opposed to gdb_test_multiple, but I don't want KFAIL activity to
> wait for it.
I completely agree with this. It seems to me that, for now, we should
just add KFAIL's using either gdb_expect or using setup_kfail+gdb_test
(with both being acceptable, depending on the test writer's
preferences). If somebody eventually writes a spiffy
gdb_test_multiple which unifies both of their virtues, then we can go
back and convert those new KFAILs to use that format (along with
existing gdb_expects). My message was only meant to brainstorm on the
possible design of such a gdb_test_multiple.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-01-03 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 21:17 Michael Elizabeth Chastain
2003-01-03 21:24 ` David Carlton [this message]
2003-01-03 21:37 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-01-03 22:03 Michael Elizabeth Chastain
2003-01-03 21:45 Michael Elizabeth Chastain
2003-01-03 21:49 ` Daniel Jacobowitz
2002-12-30 8:09 Michael Elizabeth Chastain
2002-12-30 11:41 ` Daniel Jacobowitz
2002-12-30 2:36 Michael Elizabeth Chastain
2002-12-30 8:05 ` Daniel Jacobowitz
2003-01-03 20:53 ` 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=ro1u1gqkjux.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