test suite reviews and discussions
 help / color / mirror / Atom feed
From: Lewei Yang <leweix.yang@intel.com>
To: dts@dpdk.org
Cc: Lewei Yang <leweix.yang@intel.com>
Subject: [dts][PATCH V2] tests/unit_tests_eal:remove strict timing requirements some tests
Date: Tue, 23 Nov 2021 11:00:42 +0000	[thread overview]
Message-ID: <20211123110042.127527-1-leweix.yang@intel.com> (raw)

According to dpdk commit ee00af60170b("test: remove strict timing requirements some tests"),
Remove the timing related tests from the test suites

Signed-off-by: Lewei Yang <leweix.yang@intel.com>
---
 test_plans/unit_tests_eal_test_plan.rst | 24 ------------------------
 tests/TestSuite_unit_tests_eal.py       | 21 ---------------------
 2 files changed, 45 deletions(-)

diff --git a/test_plans/unit_tests_eal_test_plan.rst b/test_plans/unit_tests_eal_test_plan.rst
index 4cb9d6b9..3b871513 100644
--- a/test_plans/unit_tests_eal_test_plan.rst
+++ b/test_plans/unit_tests_eal_test_plan.rst
@@ -189,15 +189,6 @@ Byteorder functions
 Check the result of optimized byte swap functions for each size (16-,
 32- and 64-bit).
 
-Cycles Test
-===========
-
-- Loop N times and check that the timer always increments and
-  never decrements during this loop.
-
-- Wait one second using rte_usleep() and check that the increment
-  of cycles is correct with regard to the frequency of the timer.
-
 Logs
 ====
 
@@ -244,21 +235,6 @@ Debug test
 
 - Call rte_dump_stack() and rte_dump_registers().
 
-Alarm
-=====
-
-- Check that the callback for the alarm can to be called.
-- Check that it is not possible to set alarm with invalid time value.
-- Check that it is not possible to set alarm without a callback.
-- Check that it is not possible to cancel alarm without a callback pointer.
-- Check that multiple callbacks for the alarm can be called.
-- Check that the number of removed and unremoved alarms are correct.
-- Check that no callback is called if all alarm removed.
-- Check that it is not possible to cancel an alarm within the callback itself.
-- Check that the callback which is the head of all is able to be removed.
-- Check that all alarms for the same callback can be canceled.
-
-
 CPU flags
 =========
 
diff --git a/tests/TestSuite_unit_tests_eal.py b/tests/TestSuite_unit_tests_eal.py
index 8096183c..5a3d3922 100644
--- a/tests/TestSuite_unit_tests_eal.py
+++ b/tests/TestSuite_unit_tests_eal.py
@@ -316,16 +316,6 @@ class TestUnitTestsEal(TestCase):
         self.dut.send_expect("quit", "# ")
         self.verify("Test OK" in out, "Test failed")
 
-    def test_cycles(self):
-        """
-        Run cycles autotest.
-        """
-
-        self.dut.send_expect(self.test_app_cmdline, "R.*T.*E.*>.*>", self.start_test_time)
-        out = self.dut.send_expect("cycles_autotest", "RTE>>", self.run_cmd_time)
-        self.dut.send_expect("quit", "# ")
-        self.verify("Test OK" in out, "Test failed")
-
     def test_logs(self):
         """
         Run logs autotest.
@@ -369,17 +359,6 @@ class TestUnitTestsEal(TestCase):
         self.dut.bind_interfaces_linux(driver=self.drivername)
         self.verify("Test OK" in out, "Test failed")
 
-    def test_alarm(self):
-        """
-        Run alarm autotest.
-        """
-
-        self.verify(self.env == "linuxapp", "Alarm only supported in linux env")
-        self.dut.send_expect(self.test_app_cmdline, "R.*T.*E.*>.*>", self.start_test_time)
-        out = self.dut.send_expect("alarm_autotest", "RTE>>", self.run_cmd_time)
-        self.dut.send_expect("quit", "# ")
-        self.verify("Test OK" in out, "Test failed")
-
     def test_cpuflags(self):
         """
         Run CPU flags autotest.
-- 
2.33.1


             reply	other threads:[~2021-11-23  2:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 11:00 Lewei Yang [this message]
2021-11-23 14:00 ` 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=20211123110042.127527-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).