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(124505) sid(27168) job(DTS_AUTO_2442) [V1] tests/iavf_rss_protocol_agnostic_flow: optimize script
Date: 24 Feb 2023 00:46:08 -0800 [thread overview]
Message-ID: <0ff686$o9sa56@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3131 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/124505
Subject: [V1] tests/iavf_rss_protocol_agnostic_flow: optimize script
_Testing OK_
Diff:
tests/TestSuite_iavf_rss_protocol_agnostic_flow.py
DPDK:
commit 7710b5d15a014872a3aaf646668dafa928ca8473
Author: Rongwei Liu <rongweil@nvidia.com>
Date: Tue Feb 21 12:02:01 2023 +0200
Comment: app/testpmd: fix build with -O1
DTS:
commit 11b6c1ea068db82d415f2ae0c042963d956daf69
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Thu Feb 2 13:53:18 2023 +0800
Comment: version: 23.03-rc0
Test environment and result as below:
+---------------------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+---------------------------------+----------+--------------------------------+---------------------------------+
| iavf_rss_protocol_agnostic_flow | NIC VF | run | not run |
+---------------------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/e70ff96a52694a9a9e56e1daf28ee8a5
#1: UB2004-64+216_fortville_spirit
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: NIC VF
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 12/0/0/0/12
Detail test results:
+------------------------------------------------------------------------------+------------+
| suit/case | with_patch |
+------------------------------------------------------------------------------+------------+
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp_gtpu_dl_ipv4_tcp | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp_gtpu_eh_ipv4_udp_sysmetric | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp_gtpu_ipv4 | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp_gtpu_ipv6_udp | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp_gtpu_ul_ipv4 | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp_vxlan_mac_ipv4 | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp_vxlan_mac_ipv4_pay | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp_vxlan_mac_ipv4_sysmetric | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv4_udp_vxlan_mac_ipv4_udp | n/a |
| iavf_rss_protocol_agnostic_flow/test_mac_ipv6_tcp_sysmetric | n/a |
| iavf_rss_protocol_agnostic_flow/test_multi_rules_mac_ipv4_udp_vxlan_ipv6 | n/a |
+------------------------------------------------------------------------------+------------+
DPDK STV team
next reply other threads:[~2023-02-24 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 8:46 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-24 8:42 sys_stv
2023-02-24 8:42 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='0ff686$o9sa56@fmsmga001-auth.fm.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).