From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: arrayidx.exp failures
Date: Fri, 13 Oct 2006 22:06:00 -0000 [thread overview]
Message-ID: <20061013220620.GA25411@nevyn.them.org> (raw)
In-Reply-To: <20061013163352.GJ1059@adacore.com>
On Fri, Oct 13, 2006 at 09:33:52AM -0700, Joel Brobecker wrote:
> In the meantime, are these fails an issue? For me, I have the same sort
> of issue in a smaller scale with C++ testcases, but the way I test is
> by using a smart-diff between the testcase results before and after.
Not at present.
Two or three years ago, I pushed i386-linux down almost to zero
failures. It's crept back up ever since, and x86_64-linux currently
has a whole bunch more, but I'm still working on it when I can find
time.
At work we require zero-failure testsuites for most components;
right now we're looking at an exception for GDB, which makes me quite
sad.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-10-13 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 2:17 Nick Roberts
2006-10-13 2:38 ` Joel Brobecker
2006-10-13 4:39 ` Daniel Jacobowitz
2006-10-13 16:34 ` Joel Brobecker
2006-10-13 18:50 ` Nick Roberts
2006-10-13 20:10 ` Joel Brobecker
2006-10-13 22:06 ` Daniel Jacobowitz [this message]
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=20061013220620.GA25411@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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