test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Jiang, YuX" <yux.jiang@intel.com>
To: dts@dpdk.org
Cc: JiangYu <yux.jiang@intel.com>
Subject: [dts] [dst] [PATCH V1 2/7] tests/TestSuite_virtio_user_as_exceptional_path: support meson build
Date: Fri, 18 Sep 2020 13:26:21 +0800	[thread overview]
Message-ID: <20200918052626.9525-3-yux.jiang@intel.com> (raw)
In-Reply-To: <20200918052626.9525-1-yux.jiang@intel.com>

From: JiangYu <yux.jiang@intel.com>

Adapt testpmd_name

Signed-off-by: JiangYu <yux.jiang@intel.com>
---
 tests/TestSuite_virtio_user_as_exceptional_path.py | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tests/TestSuite_virtio_user_as_exceptional_path.py b/tests/TestSuite_virtio_user_as_exceptional_path.py
index 3c04f55..3d54441 100644
--- a/tests/TestSuite_virtio_user_as_exceptional_path.py
+++ b/tests/TestSuite_virtio_user_as_exceptional_path.py
@@ -70,6 +70,7 @@ class TestVirtioUserAsExceptionalPath(TestCase):
         self.peer_pci_setup = False
         self.prepare_dpdk()
         self.app_testpmd_path = self.dut.apps_name['test-pmd']
+        self.testpmd_name = self.app_testpmd_path.split("/")[-1]
 
     def set_up(self):
         #
@@ -77,7 +78,7 @@ class TestVirtioUserAsExceptionalPath(TestCase):
         #
         # Clean the execution ENV
         self.dut.send_expect("rm -rf ./vhost-net*", "#")
-        self.dut.send_expect("killall -s INT testpmd", "#")
+        self.dut.send_expect("killall -s INT %s" % self.testpmd_name, "#")
         self.dut.send_expect("killall -s INT qemu-system-x86_64", "#")
         self.dut.send_expect("modprobe vhost-net", "#")
         self.peer_pci_setup = False
@@ -316,7 +317,7 @@ class TestVirtioUserAsExceptionalPath(TestCase):
         #
         self.dut.kill_all()
         self.dut.close_session(self.vhost_user)
-        self.dut.send_expect("killall -s INT testpmd", "#")
+        self.dut.send_expect("killall -s INT %s" % self.testpmd_name, "#")
         self.dut.send_expect("killall -s INT qemu-system-x86_64", "#")
         self.dut.send_expect("rm -rf ./vhost-net", "#")
         time.sleep(2)
-- 
2.7.4


  parent reply	other threads:[~2020-09-18  5:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  5:26 [dts] [PATCH V1 0/7] Modify virito func suites to " Jiang, YuX
2020-09-18  5:26 ` [dts] [PATCH V1 1/7] tests/TestSuite_vm2vm_virtio_pmd: " Jiang, YuX
2020-09-18  5:26 ` Jiang, YuX [this message]
2020-09-18  5:26 ` [dts] [PATCH V1 3/7] tests/TestSuite_vhost_virtio_user_interrupt: " Jiang, YuX
2020-09-18  5:26 ` [dts] [PATCH V1 4/7] tests/TestSuite_vdev_primary_secondary: " Jiang, YuX
2020-09-18  5:26 ` [dts] [PATCH V1 5/7] tests/TestSuite_loopback_virtio_user_server_mode: " Jiang, YuX
2020-09-18  5:26 ` [dts] [PATCH V1 6/7] tests/TestSuite_loopback_multi_queues: " Jiang, YuX
2020-09-18  5:26 ` [dts] [PATCH V1 7/7] tests/TestSuite_loopback_multi_paths_port_restart: " Jiang, YuX
2020-09-22  8:05   ` Ma, LihongX
2020-09-23  8:39 ` [dts] [PATCH V1 0/7] Modify virito func suites to " Tu, Lijuan

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=20200918052626.9525-3-yux.jiang@intel.com \
    --to=yux.jiang@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).