test suite reviews and discussions
 help / color / mirror / Atom feed
From: Song Jiale <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Song Jiale <songx.jiale@intel.com>, Jin Ling <jin.ling@intel.com>
Subject: [dts] [PATCH V3 2/2] test_plans/multiprocess: add 1 case
Date: Fri, 30 Dec 2022 18:28:10 +0000	[thread overview]
Message-ID: <20221230182810.1004957-2-songx.jiale@intel.com> (raw)
In-Reply-To: <20221230182810.1004957-1-songx.jiale@intel.com>

add a case to test the testpmd secondary process crash of the pf port.

Signed-off-by: Jin Ling <jin.ling@intel.com>
Signed-off-by: Song Jiale <songx.jiale@intel.com>
---

v3:
-redesign testplan

 test_plans/multiprocess_test_plan.rst | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/test_plans/multiprocess_test_plan.rst b/test_plans/multiprocess_test_plan.rst
index bfef1ca9..d3e60d9e 100644
--- a/test_plans/multiprocess_test_plan.rst
+++ b/test_plans/multiprocess_test_plan.rst
@@ -969,3 +969,26 @@ Test Case: test_multiprocess_negative_exceed_process_num
     the first and second processes should be launched successfully
     the third process should be launched failed and output should contain the following string:
     'multi-process option proc-id(2) should be less than num-procs(2)'
+
+Test Case: test_multiprocess_negative_action
+============================================
+Subcase 1: test_secondary_process_port_reset
+--------------------------------------------
+test steps
+~~~~~~~~~~
+
+1. Launch the app ``testpmd``, start primary process and secondary process with the following arguments::
+
+   ./dpdk-testpmd -l 1,2 --proc-type=auto -a 0000:17:00.0  --log-level=ice,7 -- -i  --rxq=4 --txq=4 --num-procs=2 --proc-id=0
+   ./dpdk-testpmd -l 3,4 --proc-type=auto -a 0000:17:00.0  --log-level=ice,7 -- -i  --rxq=4 --txq=4 --num-procs=2 --proc-id=1
+
+2. reset port in secondary process::
+
+    secondary process:
+      testpmd> port stop 0
+      testpmd> port reset 0
+
+expected result
+~~~~~~~~~~
+
+   Check that there are no ``core dump`` messages in the output.
\ No newline at end of file
-- 
2.25.1


  reply	other threads:[~2022-12-30 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 18:28 [dts] [PATCH V3 1/2] tests/multiprocess: add new case according to testplan Song Jiale
2022-12-30 18:28 ` Song Jiale [this message]
2022-12-30 11:03   ` [dts] [PATCH V3 2/2] test_plans/multiprocess: add 1 case Ling, Jin
2023-01-04  1:32   ` lijuan.tu
  -- strict thread matches above, loose matches on Subject: below --
2022-12-30 18:20 [dts] [PATCH V3 1/2] tests/multiprocess: add new case according to testplan Song Jiale
2022-12-30 18:20 ` [dts] [PATCH V3 2/2] test_plans/multiprocess: add 1 case Song Jiale

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=20221230182810.1004957-2-songx.jiale@intel.com \
    --to=songx.jiale@intel.com \
    --cc=dts@dpdk.org \
    --cc=jin.ling@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).