test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Zhu, WenhuiX" <wenhuix.zhu@intel.com>
To: "Yao, BingX Y" <bingx.y.yao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Yao, BingX Y" <bingx.y.yao@intel.com>,
	"Wang, FengqinX" <fengqinx.wang@intel.com>
Subject: Re: [dts] [PATCH V2] tests/flags unbind devices to DPDK
Date: Wed, 12 Dec 2018 01:20:33 +0000	[thread overview]
Message-ID: <E08767FB2CE10642B6780736EAC070F6048E5700@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1544518026-23451-1-git-send-email-bingx.y.yao@intel.com>


Tested-by: Zhu, WenhuiX <wenhuix.zhu@intel.com>

-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yaobing
Sent: Tuesday, December 11, 2018 4:47 PM
To: dts@dpdk.org
Cc: Yao, BingX Y <bingx.y.yao@intel.com>
Subject: [dts] [PATCH V2] tests/flags unbind devices to DPDK

this test just wants to make sure the memory allocation and  de-allocation behavior in clean running environment,so not having any devices bound to DPDK should be the prerequisite for running this test

Signed-off-by: yaobing <bingx.y.yao@intel.com>
---
 tests/TestSuite_unit_tests_eal.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tests/TestSuite_unit_tests_eal.py b/tests/TestSuite_unit_tests_eal.py
index 68a4cbe..74d0dfd 100644
--- a/tests/TestSuite_unit_tests_eal.py
+++ b/tests/TestSuite_unit_tests_eal.py
@@ -261,11 +261,13 @@ class TestUnitTestsEal(TestCase):
         Run eal flags autotest.
         """
 
+        self.dut.unbind_interfaces_linux()
         self.dut.send_expect(self.test_app_cmdline + ' -m 64', "R.*T.*E.*>.*>", self.start_test_time)
         # on FreeBSD need more time than other OS
         out = self.dut.send_expect("eal_flags_autotest", "RTE>>", 600)
         self.dut.send_expect("quit", "# ")
         self.verify("Test OK" in out, "Test failed")
+        self.dut.bind_interfaces_linux()
 
     def test_alarm(self):
         """
--
2.17.2

  reply	other threads:[~2018-12-12  1:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11  8:47 yaobing
2018-12-12  1:20 ` Zhu, WenhuiX [this message]
2018-12-22 20:09 ` 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=E08767FB2CE10642B6780736EAC070F6048E5700@shsmsx102.ccr.corp.intel.com \
    --to=wenhuix.zhu@intel.com \
    --cc=bingx.y.yao@intel.com \
    --cc=dts@dpdk.org \
    --cc=fengqinx.wang@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).