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 V1 0/5] migrate CBDMA related testcase to new testsuite
Date: Thu, 19 May 2022 04:33:28 -0400	[thread overview]
Message-ID: <20220519083328.2816683-1-weix.ling@intel.com> (raw)

Because of the CBDMA testcases need DPDK local patch can test, 
from DTS 22.03, we plan to migrate CBDMA related testcases to new
testsuite, for example, migrate CBDMA related testcase from 
vhost_event_idx_interrupt suite to vhost_event_idx_interrupt_cbdma suite. 

Wei Ling (5):
  test_plans/index: add vhost_event_idx_interrupt_cbdma testsuite
  test_plans/vhost_event_idx_interrupt_test_plan: migrate CBDMA related
    testcase to new testsuite
  tests/vhost_event_idx_interrupt: migrate CBDMA related testcase to new
    testsuite
  test_plans/vhost_event_idx_interrupt_cbdma_test_plan: add new
    testsuite for CBDMA related testcases
  tests/vhost_event_idx_interrupt_cbdma: new testsuite for CBDMA related
    testcases

 test_plans/index.rst                          |   1 +
 ...st_event_idx_interrupt_cbdma_test_plan.rst | 281 +++++++++++
 .../vhost_event_idx_interrupt_test_plan.rst   | 232 ---------
 tests/TestSuite_vhost_event_idx_interrupt.py  | 170 +------
 ...stSuite_vhost_event_idx_interrupt_cbdma.py | 460 ++++++++++++++++++
 5 files changed, 750 insertions(+), 394 deletions(-)
 create mode 100644 test_plans/vhost_event_idx_interrupt_cbdma_test_plan.rst
 create mode 100644 tests/TestSuite_vhost_event_idx_interrupt_cbdma.py

-- 
2.25.1


             reply	other threads:[~2022-05-19  8:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  8:33 Wei Ling [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-19  8:13 Wei Ling

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=20220519083328.2816683-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).