From: Lewei Yang <leweix.yang@intel.com>
To: dts@dpdk.org
Cc: Lewei Yang <leweix.yang@intel.com>
Subject: [dts][PATCH V1] tests/unit_tests_eal:remove unnecessary test commands
Date: Fri, 19 Nov 2021 16:59:21 +0000 [thread overview]
Message-ID: <20211119165921.30672-1-leweix.yang@intel.com> (raw)
According to dpdk commit 81169a01ff2e("test: remove unnecessary test commands"),
Nothing is referencing eal_flags_autotest and rwlock_autotest anymore,since we dropped the python wrapper.
Signed-off-by: Lewei Yang <leweix.yang@intel.com>
---
test_plans/unit_tests_eal_test_plan.rst | 21 ---------------------
tests/TestSuite_unit_tests_eal.py | 23 -----------------------
2 files changed, 44 deletions(-)
diff --git a/test_plans/unit_tests_eal_test_plan.rst b/test_plans/unit_tests_eal_test_plan.rst
index 4cb9d6b9..f4aacb67 100644
--- a/test_plans/unit_tests_eal_test_plan.rst
+++ b/test_plans/unit_tests_eal_test_plan.rst
@@ -111,27 +111,6 @@ Spinlock
for each core, in the correct order. The autotest script checks that
this order is correct.
-Rwlock
-======
-
-- There is a global rwlock and a table of rwlocks (one per lcore).
-
-- The test function takes all of these locks and launches the
- ``test_rwlock_per_core()`` function on each core (except the master).
-
- - The function takes the global write lock, display something,
- then releases the global lock.
- - Then, it takes the per-lcore write lock, display something, and
- releases the per-core lock.
- - Finally, a read lock is taken during 100 ms, then released.
-
-- The main function unlocks the per-lcore locks sequentially and
- waits between each lock. This triggers the display of a message
- for each core, in the correct order.
-
- Then, it tries to take the global write lock and display the last
- message. The autotest script checks that the message order is correct.
-
Atomic Variables
================
diff --git a/tests/TestSuite_unit_tests_eal.py b/tests/TestSuite_unit_tests_eal.py
index 8096183c..db2579ce 100644
--- a/tests/TestSuite_unit_tests_eal.py
+++ b/tests/TestSuite_unit_tests_eal.py
@@ -286,16 +286,6 @@ class TestUnitTestsEal(TestCase):
self.dut.send_expect("quit", "# ")
self.verify("Test OK" in out, "Test failed")
- def test_rwlock(self):
- """
- Run rwlock autotest.
- """
-
- self.dut.send_expect(self.test_app_cmdline, "R.*T.*E.*>.*>", self.start_test_time)
- out = self.dut.send_expect("rwlock_autotest", "RTE>>", self.run_cmd_time)
- self.dut.send_expect("quit", "# ")
- self.verify("Test OK" in out, "Test failed")
-
def test_prefetch(self):
"""
Run prefetch autotest.
@@ -356,19 +346,6 @@ class TestUnitTestsEal(TestCase):
self.dut.send_expect("quit", "# ")
self.verify("Test OK" in out, "Test failed")
- def test_flags(self):
- """
- 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.dut.bind_interfaces_linux(driver=self.drivername)
- self.verify("Test OK" in out, "Test failed")
-
def test_alarm(self):
"""
Run alarm autotest.
--
2.17.1
next reply other threads:[~2021-11-19 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 16:59 Lewei Yang [this message]
2021-11-22 15:01 ` 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=20211119165921.30672-1-leweix.yang@intel.com \
--to=leweix.yang@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).