From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Remove all remaining gdb_suppress_entire_file
Date: Tue, 08 Aug 2006 20:24:00 -0000 [thread overview]
Message-ID: <20060808202420.GA30302@nevyn.them.org> (raw)
In-Reply-To: <200608082010.k78KAB1h005794@elgar.sibelius.xs4all.nl>
On Tue, Aug 08, 2006 at 10:10:11PM +0200, Mark Kettenis wrote:
> Hmm, I guess what I really want is an UNTESTED if the failure was to
> be expected (for example the ADA tests if there is no ADA compiler on
> the system) and an error if something went wrong that shouldn't have
> gone wrong (an ICE from GCC on one of the testsuite code snippets).
> However, there probably isn't always a clear distinction between the
> two. For example, do we expect C++ snippets to compile on all
> systems? I suppose Joel's patch is progress; we can always tweak
> things later if we feel the UNTESTEDs are inappropriate.
Sounds good to me. We do expect most of the tests to compile on most
systems, except for those with "strange" dependencies - meaning
everything but C and C++ and anything with threads. But I don't see
a good way to capture this information that isn't more trouble than
it's really worth.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-08 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 0:27 Joel Brobecker
2006-07-21 0:43 ` Daniel Jacobowitz
2006-07-21 22:06 ` Mark Kettenis
2006-07-21 22:43 ` Joel Brobecker
2006-07-21 23:28 ` Daniel Jacobowitz
2006-08-08 19:00 ` Daniel Jacobowitz
2006-08-08 20:10 ` Mark Kettenis
2006-08-08 20:24 ` Daniel Jacobowitz [this message]
2006-08-09 18:05 ` Joel Brobecker
2006-08-10 4:13 ` Daniel Jacobowitz
2006-08-10 0:35 ` Daniel Jacobowitz
2006-08-10 14:12 ` Joel Brobecker
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=20060808202420.GA30302@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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