From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, songx.jiale@intel.com
Subject: [dts-test-report] |SUCCESS| pw(124845) sid(27278) job(DTS_AUTO_2464) [V1] tests/kernelpf_iavf: optimize script
Date: 07 Mar 2023 20:45:21 -0800 [thread overview]
Message-ID: <210948$pbh11v@orsmga005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3293 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/124845
Subject: [V1] tests/kernelpf_iavf: optimize script
_Testing OK_
Diff:
tests/TestSuite_kernelpf_iavf.py
DPDK:
commit 813d0eead31deb75b774524ad21e99136fbad331
Author: Tejasree Kondoj <ktejasree@marvell.com>
Date: Fri Feb 24 15:10:14 2023 +0530
Comment: crypto/cnxk: add model check for PDCP chain
DTS:
commit 964b48e223f9f3d4f1fe60502f40be7f85a9f661
Author: Song Jiale <songx.jiale@intel.com>
Date: Mon Jan 16 15:00:02 2023 +0000
Comment: tests/shutdown_api: modify the command to adapt to the changes in ethtool
Test environment and result as below:
+---------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+---------------+----------+---------------------------------+--------------------------------+
| kernelpf_iavf | CVL Only | run | not run |
+---------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/933fbc7ac96645ac9f8026a8c384cbfc
#1: UB2004-64+216_columbiaville_25g
OS: Ubuntu 20.04.5 LTS
Kernel: 5.4.0-135-generic
CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang: NA
Status: SUCCESS
Catogory: CVL Only
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 20/20/0/0/0
Detail test results:
+-------------------------------------------------------+------------+
| suit/case | with_patch |
+-------------------------------------------------------+------------+
| kernelpf_iavf/test_CRC_strip_iavf_vlan_strip_coexists | passed |
| kernelpf_iavf/test_enable_disable_iavf_CRC_strip | passed |
| kernelpf_iavf/test_iavf_dual_vlan_filter | passed |
| kernelpf_iavf/test_iavf_dual_vlan_insert | passed |
| kernelpf_iavf/test_iavf_dual_vlan_strip | passed |
| kernelpf_iavf/test_vf_basic_rxtx | passed |
| kernelpf_iavf/test_vf_broadcast | passed |
| kernelpf_iavf/test_vf_information | passed |
| kernelpf_iavf/test_vf_multicast | passed |
| kernelpf_iavf/test_vf_port_start_stop | passed |
| kernelpf_iavf/test_vf_promisc_mode | passed |
| kernelpf_iavf/test_vf_rss | passed |
| kernelpf_iavf/test_vf_rss_hash_key | passed |
| kernelpf_iavf/test_vf_rx_interrupt | passed |
| kernelpf_iavf/test_vf_statistic_reset | passed |
| kernelpf_iavf/test_vf_unicast | passed |
| kernelpf_iavf/test_vf_vlan_filter | passed |
| kernelpf_iavf/test_vf_vlan_insertion | passed |
| kernelpf_iavf/test_vf_vlan_promisc | passed |
| kernelpf_iavf/test_vf_vlan_strip | passed |
+-------------------------------------------------------+------------+
DPDK STV team
next reply other threads:[~2023-03-08 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 4:45 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-08 4:20 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='210948$pbh11v@orsmga005-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=songx.jiale@intel.com \
--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).