From: "xu,huilong" <huilongx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,huilong" <huilongx.xu@intel.com>
Subject: [dts] [PATCH V1] fix ring dump case failed
Date: Thu, 2 Mar 2017 16:05:04 +0800 [thread overview]
Message-ID: <1488441904-2699-1-git-send-email-huilongx.xu@intel.com> (raw)
when bind igb_uio on NIC. Newest testpmd will creat many ring.
Signed-off-by: xu,huilong <huilongx.xu@intel.com>
---
tests/TestSuite_unit_tests_dump.py | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tests/TestSuite_unit_tests_dump.py b/tests/TestSuite_unit_tests_dump.py
index a39fcd1..c3515da 100644
--- a/tests/TestSuite_unit_tests_dump.py
+++ b/tests/TestSuite_unit_tests_dump.py
@@ -92,8 +92,9 @@ class TestUnitTestsDump(TestCase):
m = re.compile(r"%s" % match_regex, re.S)
result = m.findall(out)
-
- self.verify(result[0][0] == 'MP_mbuf_pool_socket_0', "dump ring name failed")
+ #when we bind some nic with igb_uio. testpmd init will create 3N+1 ring, and the last ring name is MP_mbuf_pool_socket_0
+ #other ring name about nic bus ID and ring type, so will not check. we only check ring_dump function work ok
+ self.verify( 'MP_mbuf_pool_socket_0' in result[0][-1], "dump ring name failed")
def test_mempool_dump(self):
"""
--
1.9.3
next reply other threads:[~2017-03-02 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 8:05 xu,huilong [this message]
2017-03-02 8:55 ` Liu, Yong
2017-03-02 9:04 ` Xu, HuilongX
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=1488441904-2699-1-git-send-email-huilongx.xu@intel.com \
--to=huilongx.xu@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).