test suite reviews and discussions
 help / color / mirror / Atom feed
From: Herbert Guan <Herbert.Guan@arm.com>
To: "Liu, Yong" <yong.liu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>,
	"jianbo.liu@linaro.org" <jianbo.liu@linaro.org>
Subject: Re: [dts] [PATCH] tests/short_live: fixes the result parsing issue
Date: Mon, 7 Aug 2017 03:31:03 +0000	[thread overview]
Message-ID: <HE1PR08MB28093B099A6CD7EAF22A58EA86B50@HE1PR08MB2809.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <598855F2.60509@intel.com>

Marvin,

Thanks for review.  V2 patch has been submitted just now with one comments:

>> 3) pkill for l2fwd and l3fwd need to wait a while for process quit
>L2fwd and L3fwd will do the same actions after received SIGINT or SIGTERM signal. There's no need to change the signal type.
The signal type logic is not changed in this patch.  While both l2fwd and l3fwd need some time to clean up after they received the signal.  The for loop shall wait about 2 seconds before starting another process of l2fwd/l3fwd.  So "time.sleep(2)" were added after sending pkill.

Thanks,
Herbert

-----Original Message-----
From: Liu, Yong [mailto:yong.liu@intel.com]
Sent: Monday, August 7, 2017 19:59
To: Herbert Guan <Herbert.Guan@arm.com>; dts@dpdk.org; jianbo.liu@linaro.org
Subject: Re: [dts] [PATCH] tests/short_live: fixes the result parsing issue

Thanks Herbert. Some comments below.

On 08/04/2017 03:18 PM, Herbert Guan wrote:
> Fixes below issues:
> 1) corrected the scapy reslut parsing string
> 2) ensure link up for testpmd and l3fwd
Suggest to waiting for LSC event or just wait some seconds for link status updated.

> 3) pkill for l2fwd and l3fwd need to wait a while for process quit
L2fwd and L3fwd will do the same actions after received SIGINT or SIGTERM signal. There's no need to change the signal type.

> Signed-off-by: Herbert Guan<herbert.guan@arm.com>

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

      reply	other threads:[~2017-08-07  3:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04  7:18 Herbert Guan
2017-08-07  3:25 ` [dts] [PATCH v2] " Herbert Guan
2017-08-07 12:22   ` Liu, Yong
2017-08-07 11:58 ` [dts] [PATCH] " Liu, Yong
2017-08-07  3:31   ` Herbert Guan [this message]

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=HE1PR08MB28093B099A6CD7EAF22A58EA86B50@HE1PR08MB2809.eurprd08.prod.outlook.com \
    --to=herbert.guan@arm.com \
    --cc=dts@dpdk.org \
    --cc=jianbo.liu@linaro.org \
    --cc=yong.liu@intel.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;
as well as URLs for NNTP newsgroup(s).