From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |SUCCESS| pw(115772-115775) sid(24513) job(DTS_AUTO_1483) [V4, 3/3] test_plans/*:add 22.07 new feature, support in dcf mode
Date: 02 Sep 2022 00:16:13 -0700 [thread overview]
Message-ID: <e2f6d4$i4m0mv@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3209 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/115775
Subject: [V4,3/3] test_plans/*:add 22.07 new feature, support in dcf mode
_Testing OK_
Diff:
framework/settings.py
framework/dts.py
tests/TestSuite_vf_vlan.py
tests/TestSuite_vf_smoke.py
tests/TestSuite_vf_rss.py
tests/TestSuite_vf_offload.py
tests/TestSuite_vf_macfilter.py
tests/TestSuite_kernelpf_iavf.py
test_plans/vf_vlan_test_plan.rst
test_plans/vf_smoke_test_plan.rst
test_plans/vf_rss_test_plan.rst
test_plans/vf_offload_test_plan.rst
test_plans/vf_macfilter_test_plan.rst
test_plans/kernelpf_iavf_test_plan.rst
DPDK:
commit 4aee6110bb10b0225fa9562f2e48af233a9058a1
Author: Huichao Cai <chcchc88@163.com>
Date: Mon Aug 8 09:48:12 2022 +0800
Comment: ip_frag: add IPv4 fragment copy
DTS:
commit 04a93b603b6102bad7608508ceae16f31ba59ad5
Author: Ke Xu <ke1.xu@intel.com>
Date: Tue Aug 23 05:59:39 2022 +0000
Comment: tests/tso: modify get_chksum_value_and_verify to improve the performance
Test environment and result as below:
+---------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+---------------------+----------+--------------------------------+---------------------------------+
| vf_smoke | NIC VF | run | not run |
| vf_macfilter | NIC VF | run | not run |
| vf_rss | NIC VF | run | not run |
| vf_to_vf_nic_bridge | NIC VF | run | not run |
| vf_offload | NIC VF | run | not run |
| vf_vlan | NIC VF | run | not run |
| kernelpf_iavf | NIC VF | run | not run |
| ice_rss_configure | CVL Only | not run | run |
| pf_smoke | CVL Only | not run | run |
| virtio_smoke | Virtio | run | not run |
+---------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/ea59e45f753a4acba6148b2114d4e428
#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 (GCC) 10.3.0
Clang: 10.0.0-4ubuntu1
Status: SUCCESS
Catogory: Virtio
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 2/2/0/0/0
Detail test results:
+-----------------------------------+------------+
| suit/case | with_patch |
+-----------------------------------+------------+
| virtio_smoke/test_virtio_loopback | passed |
| virtio_smoke/test_virtio_pvp | passed |
+-----------------------------------+------------+
DPDK STV team
next reply other threads:[~2022-09-02 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 7:16 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-02 7:15 sys_stv
2022-09-02 7:13 sys_stv
2022-09-02 7:11 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='e2f6d4$i4m0mv@orsmga007-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).