test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "thaq@marvell.com" <thaq@marvell.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "fmasood@marvell.com" <fmasood@marvell.com>,
	"avijay@marvell.com" <avijay@marvell.com>
Subject: Re: [dts] [PATCH] tests/TestSuite_eventdev_perf.py : Moved	Unbind_eventdev_port function call to tear_down_all	tests/TestSuite_eventdev_pipeline_perf.py : Moved	Unbind_eventdev_port function call to tear_down_all
Date: Wed, 3 Jul 2019 05:56:54 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAD92EE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1561960731-10416-1-git-send-email-thaq@marvell.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of thaq@marvell.com
> Sent: Monday, July 1, 2019 1:59 PM
> To: dts@dpdk.org
> Cc: fmasood@marvell.com; avijay@marvell.com; Thanseerulhaq
> <thaq@marvell.com>
> Subject: [dts] [PATCH] tests/TestSuite_eventdev_perf.py : Moved
> Unbind_eventdev_port function call to tear_down_all
> tests/TestSuite_eventdev_pipeline_perf.py : Moved Unbind_eventdev_port
> function call to tear_down_all
> 
> From: Thanseerulhaq <thaq@marvell.com>
> 
> Signed-off-by: Thanseerulhaq <thaq@marvell.com>
> ---
>  tests/TestSuite_eventdev_perf.py          | 4 ++--
>  tests/TestSuite_eventdev_pipeline_perf.py | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/TestSuite_eventdev_perf.py
> b/tests/TestSuite_eventdev_perf.py
> index d950a87..a2520a8 100644
> --- a/tests/TestSuite_eventdev_perf.py
> +++ b/tests/TestSuite_eventdev_perf.py
> @@ -1596,11 +1596,11 @@ class
> TestEventdevPerf(TestCase,IxiaPacketGenerator):
>          """
>          Run after each test case.
>          """
> -        self.dut.send_expect("^C", "# ", 5)
> -
> self.dut.unbind_eventdev_port(port_to_unbind=self.eventdev_device_bus_i
> d)
> 
>      def tear_down_all(self):
>          """
>          Run after each test suite.
>          """
> +        self.dut.send_expect("^C", "# ", 5)
> +
> self.dut.unbind_eventdev_port(port_to_unbind=self.eventdev_device_bus_i
> d)
>          self.dut.kill_all()
> diff --git a/tests/TestSuite_eventdev_pipeline_perf.py
> b/tests/TestSuite_eventdev_pipeline_perf.py
> index 1d8a374..6a4bcad 100644
> --- a/tests/TestSuite_eventdev_pipeline_perf.py
> +++ b/tests/TestSuite_eventdev_pipeline_perf.py
> @@ -824,11 +824,11 @@ class
> TestEventdevPipelinePerf(TestCase,IxiaPacketGenerator):
>          """
>          Run after each test case.
>          """
> -        self.dut.send_expect("^C", "# ", 5)
> -
> self.dut.unbind_eventdev_port(port_to_unbind=self.eventdev_device_bus_i
> d)
> 
>      def tear_down_all(self):
>          """
>          Run after each test suite.
>          """
> +        self.dut.send_expect("^C", "# ", 5)
> +
> self.dut.unbind_eventdev_port(port_to_unbind=self.eventdev_device_bus_i
> d)
>          self.dut.kill_all()
> --
> 1.8.3.1


      reply	other threads:[~2019-07-03  5:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01  5:58 thaq
2019-07-03  5:56 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BAD92EE@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=avijay@marvell.com \
    --cc=dts@dpdk.org \
    --cc=fmasood@marvell.com \
    --cc=thaq@marvell.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).