test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xie, WeiX" <weix.xie@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xie, WeiX" <weix.xie@intel.com>
Subject: Re: [dts] [PATCH V1] tests/runtime_vf_queue_number:restore i40e vf to	iavf when bind i40evf failed
Date: Thu, 2 Jul 2020 07:20:07 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC68E34@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200702071018.8551-1-weix.xie@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Xie wei
> Sent: 2020年7月2日 15:10
> To: dts@dpdk.org
> Cc: Xie, WeiX <weix.xie@intel.com>
> Subject: [dts] [PATCH V1] tests/runtime_vf_queue_number:restore i40e vf to
> iavf when bind i40evf failed
> 
> call interface to determine which kernel driver to bind on vm, and the case just
> verifies queue number.
> 
> Signed-off-by: Xie wei <weix.xie@intel.com>
> ---
>  tests/TestSuite_runtime_vf_queue_number.py | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/TestSuite_runtime_vf_queue_number.py
> b/tests/TestSuite_runtime_vf_queue_number.py
> index 940e36a..93caf9e 100644
> --- a/tests/TestSuite_runtime_vf_queue_number.py
> +++ b/tests/TestSuite_runtime_vf_queue_number.py
> @@ -365,7 +365,7 @@ class TestRuntimeVfQn(TestCase):
>          host_eal_param = '-w %s,queue-num-per-vf=2 --file-prefix=test1 --socket-
> mem 1024,1024' % self.pf_pci
>          self.host_testpmd.start_testpmd(self.pmdout.default_cores, param='',
> eal_param=host_eal_param)
>          self.vm0_testpmd = PmdOutput(self.vm_dut_0)
> -        self.vm0_testpmd.execute_cmd("./usertools/dpdk-devbind.py -b
> i40evf %s" % self.vm_dut_0.ports_info[0]['pci'], expected='# ')
> +        self.vm_dut_0.restore_interfaces()
>          # wait few seconds for link ready
>          countdown = 60
>          while countdown:
> @@ -380,7 +380,7 @@ class TestRuntimeVfQn(TestCase):
>                  countdown -= 1
>                  continue
>          output = self.vm0_testpmd.execute_cmd("ethtool -S %s" % inf,
> expected='# ')
> -        self.verify("tx-0.packets: 0" in output and "tx-1.packets: 0" in output, "VF0
> rxq and txq number is not 2.")
> +        self.verify("tx-0.packets" in output and "tx-1.packets" in output, "VF0 rxq
> and txq number is not 2.")
> 
>      def tear_down(self):
>          self.stop_vm0()
> --
> 2.17.1


      parent reply	other threads:[~2020-07-02  7:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02  7:10 Xie wei
2020-07-02  7:11 ` Xie, WeiX
2020-07-02  7:20 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC68E34@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=weix.xie@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).