Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH]testsuite: test for disconnected-tracing
Date: Thu, 10 May 2012 11:57:00 -0000	[thread overview]
Message-ID: <4FABAD08.5020305@redhat.com> (raw)
In-Reply-To: <4FAB41A5.2020802@mentor.com>

On 05/10/2012 05:18 AM, Hui Zhu wrote:

> On 04/11/12 13:44, Hui Zhu wrote:
>> On 04/05/12 19:50, Pedro Alves wrote:
>>> On 04/05/2012 09:14 AM, Hui Zhu wrote:
>>>
>>>> I post a new version patch according to your comments.
>>>> And I have test it with gdb-7.4 and got fail.
>>>
>>>
>>> Thanks.  Only a few nits remain, and this is technically ready to
>>> check in.  See below.
>>>
>>> However, what's the status of your copyright assignment?  Last I
>>> heard (and from what I see in FSF's copyright assignment records), we
>>> still can't accept changes from you on behalf of Mentor.  :-(
>>
>> What I got is it is OK now.  I will send you a mail and cc the people that about the law.
> 
> Hi Pedro,
> 
> The copyright issue is OK now.  


Yep, took a while, but it's sorted now.  Thanks for your patience.

> Do you think I can check in this patch?


I took another look at the patch, and I now notice you didn't address
some of my early comments in <http://sourceware.org/ml/gdb-patches/2012-03/msg00987.html>:

> Please always look at the resulting messages in gdb.sum:
..
> There are duplicate messages here.  See
> <http://sourceware.org/gdb/wiki/GDBTestcaseCookbook#Make_sure_test_messages_are_unique>.
>
> I'd lowercase the "First", etc., in the test messages.  It's much more common.

This is what I get now:

>cat testsuite/gdb.sum| grep PASS | sort | uniq -c | sort -nr
      2 PASS: gdb.trace/disconnected-tracing.exp: reconnect after unload
      2 PASS: gdb.trace/disconnected-tracing.exp: disconnect
      1 PASS: gdb.trace/disconnected-tracing.exp: tstart
      1 PASS: gdb.trace/disconnected-tracing.exp: trace main
      1 PASS: gdb.trace/disconnected-tracing.exp: Third info tracepoints
      1 PASS: gdb.trace/disconnected-tracing.exp: set disconnected-tracing on
      1 PASS: gdb.trace/disconnected-tracing.exp: set confirm off
      1 PASS: gdb.trace/disconnected-tracing.exp: Second info tracepoints
      1 PASS: gdb.trace/disconnected-tracing.exp: Fourth info tracepoints
      1 PASS: gdb.trace/disconnected-tracing.exp: First info tracepoints

Yao also made a valid comment here:

<http://sourceware.org/ml/gdb-patches/2012-04/msg00124.html>

that doesn't appear to have been addressed.

-- 
Pedro Alves


  reply	other threads:[~2012-05-10 11:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 14:00 Hui Zhu
2012-03-28 18:51 ` Tom Tromey
2012-03-29  1:17   ` Hui Zhu
2012-03-29 11:37     ` Pedro Alves
2012-04-05  8:14       ` Hui Zhu
2012-04-05 11:51         ` Pedro Alves
2012-04-11  5:58           ` Hui Zhu
2012-05-10  4:19             ` Hui Zhu
2012-05-10 11:57               ` Pedro Alves [this message]
2012-05-10 15:05                 ` Hui Zhu
2012-05-10 15:10                   ` Pedro Alves
2012-05-11  0:59                     ` Hui Zhu
2012-05-11 10:45                       ` Pedro Alves
2012-05-14  2:25                         ` Hui Zhu
2012-04-08  7:59         ` Yao Qi

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=4FABAD08.5020305@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    --cc=tromey@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