test suite reviews and discussions
 help / color / mirror / Atom feed
From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V2] tests/l3fwd_func: fix script
Date: Tue, 17 May 2022 15:48:59 +0800	[thread overview]
Message-ID: <20220517074859.1715527-1-songx.jiale@intel.com> (raw)

fix 2 issue:
  1.When DUT and tester ports are cross connected, the information of interconnection 
    ports cannot be obtained correctly.
  2.tcpdump timeout, increase the '-n' to skip the tcpdump reverse domain name 
    resolution operation.

Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
 tests/TestSuite_l3fwd_func.py | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tests/TestSuite_l3fwd_func.py b/tests/TestSuite_l3fwd_func.py
index 7340c09d..c2a3988b 100644
--- a/tests/TestSuite_l3fwd_func.py
+++ b/tests/TestSuite_l3fwd_func.py
@@ -49,7 +49,8 @@ class TestL3fwdFunc(TestCase):
         self.app_path = self.dut.build_dpdk_apps("examples/l3fwd")
         self.pkt = Packet()
         self.dport_info0 = self.dut.ports_info[self.dut_ports[0]]
-        self.tport_info0 = self.tester.ports_info[self.dut_ports[0]]
+        tport = self.tester.get_local_port(self.dut_ports[0])
+        self.tport_info0 = self.tester.ports_info[tport]
         self.tport_intf0 = self.tport_info0["intf"]
         # judgment is added to avoid errors caused by the absence of port 1
         if len(self.dut_ports) >= 2:
@@ -132,7 +133,7 @@ class TestL3fwdFunc(TestCase):
         :return:
         """
         out = self.tester.send_expect(
-            "tcpdump -r /tmp/tester/sniff_%s.pcap" % (self.tport_intf0),
+            "tcpdump -n -r /tmp/tester/sniff_%s.pcap" % (self.tport_intf0),
             "# ",
             timeout=30,
         )
-- 
2.17.1


             reply	other threads:[~2022-05-17  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17  7:48 Jiale Song [this message]
2022-05-17  8:22 ` Chen, LingliX
2022-05-18  8:58 ` lijuan.tu

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=20220517074859.1715527-1-songx.jiale@intel.com \
    --to=songx.jiale@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).