From: Lijuan Tu <lijuanx.a.tu@intel.com>
To: dts@dpdk.org
Cc: Lijuan Tu <lijuanx.a.tu@intel.com>
Subject: [dts] [PATCH]tests vf_to_vf_nic_bridge:fix "killall tcpdump" won't get usefull infomation
Date: Mon, 11 Jul 2016 09:49:08 +0800 [thread overview]
Message-ID: <1468201748-42995-1-git-send-email-lijuanx.a.tu@intel.com> (raw)
we use "killall tcpdump" to get "x packets captured" infomation before.
but on some os ,it is invalid.
Signed-off-by: Lijuan Tu <lijuanx.a.tu@intel.com>
---
tests/TestSuite_vf_to_vf_nic_bridge.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/TestSuite_vf_to_vf_nic_bridge.py b/tests/TestSuite_vf_to_vf_nic_bridge.py
index 4137404..9c5548b 100644
--- a/tests/TestSuite_vf_to_vf_nic_bridge.py
+++ b/tests/TestSuite_vf_to_vf_nic_bridge.py
@@ -187,7 +187,7 @@ class TestVF2VFBridge(TestCase):
self.vm0_dut.restore_interfaces()
self.vm0_ports = self.vm0_dut.get_ports('any')
vf0_intf = self.vm0_dut.ports_info[self.vm0_ports[0]]['intf']
- self.vm0_dut.send_expect('tcpdump -i %s -s 1000 > /dev/null &' % vf0_intf, '#', 30)
+ self.vm0_dut.send_expect('tcpdump -i %s -s 1000 ' % vf0_intf, 'tcpdump', 30)
self.vm1_ports = self.vm1_dut.get_ports('any')
self.prepare_pktgen(self.vm1_dut)
@@ -204,7 +204,7 @@ class TestVF2VFBridge(TestCase):
self.send_stream_pktgen(self.vm1_dut)
self.stop_stream_pktgen(self.vm1_dut)
- recv_tcpdump = self.vm0_dut.send_expect('killall tcpdump', '#', 30)
+ recv_tcpdump = self.vm0_dut.send_expect('^C', '#', 30)
time.sleep(5)
recv_pattern = re.compile("(\d+) packets captured")
recv_info = recv_pattern.search(recv_tcpdump)
--
2.5.0
next reply other threads:[~2016-07-11 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 1:49 Lijuan Tu [this message]
2016-07-12 1:15 ` Liu, Yong
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=1468201748-42995-1-git-send-email-lijuanx.a.tu@intel.com \
--to=lijuanx.a.tu@intel.com \
--cc=dts@dpdk.org \
/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).