Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
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:10:00 -0000	[thread overview]
Message-ID: <200608082010.k78KAB1h005794@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060808190052.GG24779@nevyn.them.org> (message from Daniel 	Jacobowitz on Tue, 8 Aug 2006 15:00:52 -0400)

> Date: Tue, 8 Aug 2006 15:00:52 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> > gdb_suppress_entire_file used to issue a WARNING.  There was never
> > supposed to be any ERROR - they were caused by cascading failures,
> > DejaGNU getting confused, and usually the first symptom was a fake
> > "timeout" while trying to load a file into GDB.  And that generated an
> > ERROR.
> > 
> > After Joel's patch I believe we'll only get an UNTESTED.  If you'd
> > rather we could leave the warning?
> 
> Hi Mark,
> 
> Did you have any opinion on this?  One way or another I'd like to get
> this patch squared away.

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.

Mark


  reply	other threads:[~2006-08-08 20:10 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 [this message]
2006-08-08 20:24         ` Daniel Jacobowitz
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=200608082010.k78KAB1h005794@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --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