From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, weiyuanx.li@intel.com
Subject: [dts-test-report] |SUCCESS| pw(119979-119986) sid(25828) job(DTS_AUTO_1885) [V3, 8/8] tests/vlan: modify script and test plan to support i40e fimware >= 8.4
Date: 21 Nov 2022 00:46:32 -0800 [thread overview]
Message-ID: <8251fc$k2lt1a@orsmga001-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4457 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/119986
Subject: [V3,8/8] tests/vlan: modify script and test plan to support i40e fimware >= 8.4
_Testing OK_
Diff:
test_plans/dual_vlan_test_plan.rst
tests/TestSuite_dual_vlan.py
test_plans/ipgre_test_plan.rst
tests/TestSuite_ipgre.py
test_plans/vlan_ethertype_config_test_plan.rst
tests/TestSuite_vlan_ethertype_config.py
test_plans/vlan_test_plan.rst
tests/TestSuite_vlan.py
DPDK:
commit 903ec2b1b49e496815c016b0104fd655cd972661
Author: Taekyung Kim <kim.tae.kyung@navercorp.com>
Date: Thu Nov 10 13:09:43 2022 +0900
Comment: vdpa/ifc: handle data path update failure
DTS:
commit 666a7336ff5677cd05fc52698201a8c00d3e3e83
Author: Wei Ling <weix.ling@intel.com>
Date: Mon Nov 21 13:39:23 2022 +0800
Comment: test_plans/ntb_test_plan: add start step in testcase2
Test environment and result as below:
+-----------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+-----------------------+----------+---------------------------------+--------------------------------+
| ipgre | NIC PF | not run | run |
| dual_vlan | NIC PF | not run | run |
| vlan_ethertype_config | NIC PF | not run | run |
| vlan | NIC PF | not run | run |
+-----------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/dc6d484ccc464c3d87c8d483743e5b20
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 20.04.4 LTS
Kernel: 5.11.0-37-generic
CPU: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang: 10.0.0-4ubuntu1
Status: SUCCESS
Catogory: NIC PF
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 21/19/0/0/2
Detail test results:
+--------------------------------------------------------------------------+------------+
| suit/case | with_patch |
+--------------------------------------------------------------------------+------------+
| dual_vlan/test_vlan_filter_config | passed |
| dual_vlan/test_vlan_filter_table | passed |
| dual_vlan/test_vlan_insert_config | passed |
| dual_vlan/test_vlan_random_test | passed |
| dual_vlan/test_vlan_strip_config | passed |
| dual_vlan/test_vlan_stripq_config | n/a |
| dual_vlan/test_vlan_synthetic_test | passed |
| dual_vlan/test_vlan_tpid_config | passed |
| ipgre/test_GRE_ipv4_packet_detect | passed |
| ipgre/test_GRE_ipv6_packet_detect | passed |
| ipgre/test_GRE_packet_chksum_offload | passed |
| vlan/test_vlan_disable_receipt | passed |
| vlan/test_vlan_enable_receipt_strip_off | passed |
| vlan/test_vlan_enable_receipt_strip_on | passed |
| vlan/test_vlan_enable_vlan_insertion | passed |
| vlan_ethertype_config/test_add_vlan_tag_identifier_with_change_vlan_tpid | passed |
| vlan_ethertype_config/test_vlan_change_tpid | passed |
| vlan_ethertype_config/test_vlan_filter_on_off | passed |
| vlan_ethertype_config/test_vlan_header_insert_with_change_vlan_tpid | passed |
| vlan_ethertype_config/test_vlan_header_strip_with_change_vlan_tpid | passed |
| vlan_ethertype_config/test_vlan_qinq_tpid | n/a |
+--------------------------------------------------------------------------+------------+
DPDK STV team
next reply other threads:[~2022-11-21 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 8:46 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-21 8:56 sys_stv
2022-11-21 8:19 sys_stv
2022-11-21 8:17 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='8251fc$k2lt1a@orsmga001-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@dpdk.org \
--cc=weiyuanx.li@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).