From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
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 08:12:00 -0000 [thread overview]
Message-ID: <17837.55904.753653.372700@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070117060126.GB19331@nevyn.them.org>
> > > 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.
I'm not saying it is a good test, just that it's not completely useless. If
someone who can see the fail fixes it, then clearly that's an improvement.
> > 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.
I've just eliminated six fails in mi-basics.exp and mi2-basics.exp that had
been around for years. No-one seemed that worried about them. I think we need
a balanced approach in these matters. I certainly won't knowingly add any new
failures.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-01-17 8:12 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
2007-01-17 8:12 ` Nick Roberts [this message]
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=17837.55904.753653.372700@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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