test suite reviews and discussions
 help / color / mirror / Atom feed
From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V2] tests/dpdk_hugetlbfs_mount_size: fix verify failed can't umount huge page
Date: Tue, 15 Feb 2022 14:26:44 +0800	[thread overview]
Message-ID: <20220215062644.2136279-1-weix.ling@intel.com> (raw)

1.Add kill testpmd step in set_up.
2.Add kill testpmd before umount hege page in tear_down.

Signed-off-by: Wei Ling <weix.ling@intel.com>
---
 tests/TestSuite_dpdk_hugetlbfs_mount_size.py | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tests/TestSuite_dpdk_hugetlbfs_mount_size.py b/tests/TestSuite_dpdk_hugetlbfs_mount_size.py
index c7da7b9e..d116810d 100644
--- a/tests/TestSuite_dpdk_hugetlbfs_mount_size.py
+++ b/tests/TestSuite_dpdk_hugetlbfs_mount_size.py
@@ -72,13 +72,13 @@ class DpdkHugetlbfsMountSize(TestCase):
             self.socket_mem2 = "0,2048"
         self.umount_huge([DEFAULT_MNT])
         self.app_path = self.dut.apps_name['test-pmd']
-
+        self.testpmd_name = self.app_path.split("/")[-1]
 
     def set_up(self):
         """
         Run before each test case.
         """
-        pass
+        self.dut.send_expect("killall -s INT %s" % self.testpmd_name, "#")
 
     def close_session(self):
         self.dut.close_session(self.session_first)
@@ -265,6 +265,7 @@ class DpdkHugetlbfsMountSize(TestCase):
         Run after each test case.
         """
         # If case fails, the mount should be cancelled to avoid affecting next cases
+        self.dut.send_expect("killall -s INT %s" % self.testpmd_name, "#")
         self.umount_huge([MNT_PATH[0], MNT_PATH[1], MNT_PATH[2]])
         self.dut.kill_all()
         time.sleep(2)
-- 
2.25.1


             reply	other threads:[~2022-02-15  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  6:26 Wei Ling [this message]
2022-02-16  1:41 ` Tu, Lijuan
2022-02-16  1:52   ` Ling, WeiX
2022-02-16  2:28     ` 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=20220215062644.2136279-1-weix.ling@intel.com \
    --to=weix.ling@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).