From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: MI failures related to string printing
Date: Tue, 16 Jan 2007 20:44:00 -0000 [thread overview]
Message-ID: <20070116204407.784494F6C7@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200701160941.59975.ghost@cs.msu.su>
> > If your just talking about the one FAIL in mi-var-child.exp, why not just
> > mark it as an XFAIL? I see that the other XFAIL actually passes (for me,
> > at least).
I mean when "FIXME" is removed from the output string.
> Why should it be an XFAIL? The test was working fine before your change,
> and I see no reason why the test cannot be modified to always pass.
The aim of the testsuite is to test GDB and not just get 100% pass rate (except
when we're on performance related pay!). The test presumably has value on
systems where it passes. I'm sure it can be modified to always pass but that's
only worthwhile if it remains a meaningful test. I don't know how to devise
such a test because it doesn't fail for me now.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-01-16 20:44 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 [this message]
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
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=20070116204407.784494F6C7@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--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