test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "Peng, ZhihongX" <zhihongx.peng@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, ZhihongX" <zhihongx.peng@intel.com>
Subject: Re: [dts] [PATCH V1] Before the exception exit, it needs to be re-bound to the DPDK.
Date: Tue, 5 Nov 2019 01:53:05 +0000	[thread overview]
Message-ID: <BE1E572D0441E34284F1F8B7AC28F1970BB25F47@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20191104062109.15705-1-zhihongx.peng@intel.com>

Hi, zhihong
Please add the prefix 'dir/suite_name' to you subject, like 'tests/userspace_ethtool: Before the exception exit, it needs to be re-bound to the DPDK'
And becasuse the ports number greather than 1, as you modify, if the verify failed on second port, it will only re-bound the second port, the first port is also bind on system driver.
I think you should optimization the code.
By the way, in this suite, case test_dump_driver_info also have this issue, please modify code together.

-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Peng Zhihong
Sent: Monday, November 4, 2019 2:21 PM
To: dts@dpdk.org
Cc: Peng, ZhihongX <zhihongx.peng@intel.com>
Subject: [dts] [PATCH V1] Before the exception exit, it needs to be re-bound to the DPDK.

Before the exception exit, it needs to be re-bound to the DPDK.

Signed-off-by: Peng Zhihong <zhihongx.peng@intel.com>
---
 tests/TestSuite_userspace_ethtool.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tests/TestSuite_userspace_ethtool.py b/tests/TestSuite_userspace_ethtool.py
index 116fd3a..16d7f5c 100644
--- a/tests/TestSuite_userspace_ethtool.py
+++ b/tests/TestSuite_userspace_ethtool.py
@@ -335,7 +335,9 @@ class TestUserspaceEthtool(TestCase, IxiaPacketGenerator):
             # get linux interface
             intf = netdev.get_interface_name()
             out = self.dut.send_expect("ethtool -d %s raw off file %s" % (intf, portinfo['reg_file']), "# ")
-            self.verify(("register" in out and "CTRL" in out), "Failed to dump %s registers" % intf)
+            if "register" not in out or "CTRL" not in out:
+                portinfo['net_dev'].bind_driver(portinfo['ori_driver'])
+                raise VerifyFailure("Failed to dump %s registers" % intf)
 
         for index in range(len(self.ports)):
             # bind to original driver
-- 
2.17.1


      reply	other threads:[~2019-11-05  1:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04  6:21 Peng Zhihong
2019-11-05  1:53 ` Ma, LihongX [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=BE1E572D0441E34284F1F8B7AC28F1970BB25F47@SHSMSX101.ccr.corp.intel.com \
    --to=lihongx.ma@intel.com \
    --cc=dts@dpdk.org \
    --cc=zhihongx.peng@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).