From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Remove all remaining gdb_suppress_entire_file
Date: Fri, 21 Jul 2006 22:43:00 -0000 [thread overview]
Message-ID: <20060721224329.GA1312@adacore.com> (raw)
In-Reply-To: <200607212205.k6LM5sNC003058@elgar.sibelius.xs4all.nl>
> Most of these are checking compile failures. Are we still seeing some
> sort of ERROR about that in the testsuite output, or just UNTESTED?
The worst case I've had in the past was timeouts, it's been a while
though. But the reason I thought it was a good idea was that it didn't
seem to make sense to me to run the testcase anyway if we didn't manage
to build the test executable, did it. In other words, why announce that
all following tests will fail and run them nonetheless? It's not the
only reason because I wouldn't mind if that was just the case. But I
remember telling myself that I could have avoided a lot of grief at
certain times if we stopped the testcase after failing to do the compile.
The failures these tests detect put the testcase into a sort of degraded
mode, and dejagnu is not so good sometimes in these modes...
Sorry that my memory is so vague. Perhaps Daniel has more concrete
examples in mind...
--
Joel
next prev parent reply other threads:[~2006-07-21 22:43 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 [this message]
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
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=20060721224329.GA1312@adacore.com \
--to=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