From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: MI failures related to string printing
Date: Wed, 17 Jan 2007 06:01:00 -0000 [thread overview]
Message-ID: <20070117060126.GB19331@nevyn.them.org> (raw)
In-Reply-To: <17837.29931.145384.679968@kahikatea.snap.net.nz>
On Wed, Jan 17, 2007 at 01:59:23PM +1300, Nick Roberts wrote:
> > Don't you think that a test that randomly fails depending on compiler
> > version and the address at which the binary happens to load is completely
> > useless.
>
> It has value because it doesn't fail for everyone.
Sorry, Vladimir is correct. A test which fails intermittently (and
even if it's consistent for some people that doesn't change the fact
that this is a fundamentally intermittent problem) is not a good test.
> By keeping the previous results and comparing them. I always get many fails
> when I run the testsuite.
I am working on eliminating every single one of those failures; please
do not add more.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-17 6:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200701121351.29310.vladimir@codesourcery.com>
[not found] ` <17831.31430.442855.801431@kahikatea.snap.net.nz>
2007-01-16 2:08 ` Vladimir Prus
2007-01-16 5:50 ` Nick Roberts
2007-01-16 6:42 ` Vladimir Prus
2007-01-16 20:44 ` Nick Roberts
2007-01-16 23:06 ` Vladimir Prus
2007-01-17 0:59 ` Nick Roberts
2007-01-17 6:01 ` Daniel Jacobowitz [this message]
2007-01-17 8:12 ` Nick Roberts
2007-01-16 21:23 ` Mark Kettenis
2007-01-16 22:16 ` Nick Roberts
2007-01-17 6:06 ` Daniel Jacobowitz
2007-01-17 21:44 ` Mark Kettenis
2007-01-17 22:19 ` Daniel Jacobowitz
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=20070117060126.GB19331@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--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