From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |SUCCESS| pw(113666-113667) sid(23880) job(DTS_AUTO_1282) [V2, 2/2] tests/queue_start_stop: modify script according to dpdk code change
Date: 05 Jul 2022 00:05:14 -0700 [thread overview]
Message-ID: <b63a69$gt6deb@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2332 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/113667
Subject: [V2,2/2] tests/queue_start_stop: modify script according to dpdk code change
_Testing OK_
Diff:
tests/TestSuite_dynamic_queue.py
test_plans/dynamic_queue_test_plan.rst
tests/TestSuite_queue_start_stop.py
test_plans/queue_start_stop_test_plan.rst
DPDK:
commit ad42b228c6e26e88b16504153a9338f9b387d2e7
Author: Archana Muniganti <marchana@marvell.com>
Date: Thu Jun 30 16:51:23 2022 +0530
Comment: examples/fips_validation: fix print for zero length payload
DTS:
commit ce08b31ea6b7124ed52cbcb8a261b826a2c28d93
Author: Jiale Song <songx.jiale@intel.com>
Date: Wed Jun 29 17:35:53 2022 +0000
Comment: tests/multiprocess: modify script to suport i40e driver
Test environment and result as below:
+------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+------------------+----------+---------------------------------+--------------------------------+
| queue_start_stop | NIC PF | not run | run |
| dynamic_queue | NIC PF | not run | run |
+------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/09036e5794bd4e01a2ab3078322c77b1
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 20.04.4 LTS
Kernel: 5.8.0-51-generic
CPU: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
GCC: gcc (GCC) 10.3.0
Clang: 10.0.0-4ubuntu1
Status: SUCCESS
Catogory: NIC PF
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 5/5/0/0/0
Detail test results:
+----------------------------------------+------------+
| suit/case | with_patch |
+----------------------------------------+------------+
| dynamic_queue/test_rxq_chgring_setup | passed |
| dynamic_queue/test_rxq_setup | passed |
| dynamic_queue/test_txq_chgring_setup | passed |
| dynamic_queue/test_txq_setup | passed |
| queue_start_stop/test_queue_start_stop | passed |
+----------------------------------------+------------+
DPDK STV team
next reply other threads:[~2022-07-05 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 7:05 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-05 7:00 sys_stv
2022-07-05 6:58 sys_stv
2022-07-05 6:56 sys_stv
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='b63a69$gt6deb@orsmga006-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@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).