From: Elena Zannoni <ezannoni@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
fnasser@redhat.com, <gdb-patches@sources.redhat.com>
Subject: Re: [RFA/MI testsuite] Add pthreads tests
Date: Tue, 24 Sep 2002 12:20:00 -0000 [thread overview]
Message-ID: <15760.47731.146760.523431@localhost.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209160919450.1395-100000@valrhona.uglyboxes.com>
Keith Seitz writes:
> On Sun, 15 Sep 2002, Elena Zannoni wrote:
>
> > I wonder if we should name the file gdb669.exp.
>
> The file tests more than just gdb/669: it tests all of the MI thread
> commands. I have more tests for this file which test the syncronization of
> the MI and console command interpreters.
>
Could you split it in two files? one .exp just for 669 with the kfail,
and one .exp for the rest. Even if you have to duplicate one proc or
two. I thing it'll make things easier in the long run. So the
'generic' testfile can evolve freely.
> I would add the setup_kfail bit, as Fernando recommends, but I'm afraid
> that the tests are rather undeterministic when it comes to gdb/669 -- any
> one of the checks for the syncronization could fail. (Maybe it doesn't
> matter?)
>
I think we can refine the test as we go, we are doing this all the
times anyway. I am not too concerned.
Elena
> > OK otherwise.
>
> I'll wait to here from Fernando or you on the kfail bit, and then I'll
> commit it (and submit a patch to fix gdb/669).
>
> Keith
next prev parent reply other threads:[~2002-09-24 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 16:15 Keith Seitz
2002-09-15 12:18 ` Elena Zannoni
2002-09-16 9:21 ` Keith Seitz
2002-09-24 12:20 ` Elena Zannoni [this message]
2002-09-24 12:36 ` Keith Seitz
2002-09-25 8:46 ` Fernando Nasser
2002-09-25 9:08 ` Keith Seitz
2002-09-16 7:30 ` Fernando Nasser
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=15760.47731.146760.523431@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@redhat.com \
/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