From: "Yao, BingX Y" <bingx.y.yao@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhang, YanX A" <yanx.a.zhang@intel.com>
Subject: Re: [dts] [PATCH V1] tests/TestSuite_vm_hotplug:Optimize the tcpdump command
Date: Fri, 27 Sep 2019 07:52:06 +0000 [thread overview]
Message-ID: <95BCD24840F32441BEA74E0F8A31839E05904DDB@SHSMSX106.ccr.corp.intel.com> (raw)
In-Reply-To: <1569569200-139992-1-git-send-email-yanx.a.zhang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Tested-by: Yao, BingX Y <bingx.y.yao@intel.com>
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhang,yan
Sent: Friday, September 27, 2019 3:27 PM
To: dts@dpdk.org
Cc: Zhang, YanX A <yanx.a.zhang@intel.com>
Subject: [dts] [PATCH V1] tests/TestSuite_vm_hotplug:Optimize the tcpdump command
Optimize the tcpdump command to improve script stability.
Signed-off-by: zhang,yan <yanx.a.zhang@intel.com>
---
tests/TestSuite_vm_hotplug.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/TestSuite_vm_hotplug.py b/tests/TestSuite_vm_hotplug.py index 87edad6..d0c75ac 100644
--- a/tests/TestSuite_vm_hotplug.py
+++ b/tests/TestSuite_vm_hotplug.py
@@ -232,7 +232,7 @@ class TestVmHotplug(TestCase):
def start_tcpdump(self, iface_list):
for iface in iface_list:
self.tester.send_expect("rm -rf tcpdump%s.out" % iface, "#")
- self.tester.send_expect("tcpdump -i %s 2>tcpdump%s.out &" % (iface, iface), "#")
+ self.tester.send_expect("tcpdump -c 1500 -i %s -vv -n
+ 2>tcpdump%s.out &" % (iface, iface), "#")
time.sleep(1)
def get_tcpdump_package(self, iface_list):
--
2.17.2
[-- Attachment #2: TestVmHotplug.log --]
[-- Type: application/octet-stream, Size: 893190 bytes --]
next prev parent reply other threads:[~2019-09-27 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 7:26 zhang,yan
2019-09-27 7:52 ` Yao, BingX Y [this message]
2019-10-12 5:56 ` Tu, Lijuan
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=95BCD24840F32441BEA74E0F8A31839E05904DDB@SHSMSX106.ccr.corp.intel.com \
--to=bingx.y.yao@intel.com \
--cc=dts@dpdk.org \
--cc=yanx.a.zhang@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).