From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: chenyux.huang@intel.com, lijuan.tu@intel.com,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
daxuex.gao@intel.com
Subject: [dpdk-test-report]|SUCCESS | dpdk|cee226c934| Intel-Testing
Date: 27 Nov 2022 03:16:00 -0800 [thread overview]
Message-ID: <510f81$l6m1nh@fmsmga004-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3850 bytes --]
Test-Label: intel-Testing
Test-Status: SUCCESS
_Testing PASS
DPDK git repo: dpdk
commit cee226c934e2a73f1b7b7d26e80d6719ca21a457
Author: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date: Fri Dec 3 08:54:15 2021 +0100
devtools: report commit ID on partial fixes
The candidate list for backports lists partial fixes like:
"(21.02 (partially fixed in 21.08))"
That is useful to identify fixes meant for later releases, but
indirectly applying to older ones as well.
While the devscript has no access to the stable tree to fully check
if the respective interim commit is present there, reporting the commit
id will still help to check it later - because only if the interim commit
id is in the stable tree, then also the new fix is a real candidate
for backporting.
The above would become "(21.02 (partially fixed in c30751afc360 @ 21.08))"
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Acked-by: Luca Boccassi <bluca@debian.org>
Acked-by: Kevin Traynor <ktraynor@redhat.com>
Acked-by: Xueming Li <xuemingl@nvidia.com>
Testing Summary : 18 Case Done, 18 Successful, 0 Failures
Testbed #1: 9 Case Done, 9 Successful, 0 Failures
* Test result details:
+-------------+---------------------------+-------+
| suite | case | status|
+-------------+---------------------------+-------+
| asan_smoke | test_rxtx_with_ASan_enable| passed|
| pf_smoke | test_pf_jumbo_frames | passed|
| pf_smoke | test_pf_rss | passed|
| pf_smoke | test_pf_tx_rx_queue | passed|
| vf_smoke | test_vf_jumbo_frames | passed|
| vf_smoke | test_vf_rss | passed|
| vf_smoke | test_vf_tx_rx_queue | passed|
| virtio_smoke| test_virtio_loopback | passed|
| virtio_smoke| test_virtio_pvp | passed|
+-------------+---------------------------+-------+
* Environment:
OS : Ubuntu 20.04.5 LTS
Kernel : 5.8.0-63-generic
GCC : 9.4.0-1ubuntu1~20.04.1
NIC : Ethernet Controller E810-C for SFP
Target : x86_64-native-linuxapp-gcc
Testbed #2: 9 Case Done, 9 Successful, 0 Failures
* Test result details:
+-------------+---------------------------+-------+
| suite | case | status|
+-------------+---------------------------+-------+
| asan_smoke | test_rxtx_with_ASan_enable| passed|
| pf_smoke | test_pf_jumbo_frames | passed|
| pf_smoke | test_pf_rss | passed|
| pf_smoke | test_pf_tx_rx_queue | passed|
| vf_smoke | test_vf_rss | passed|
| vf_smoke | test_vf_tx_rx_queue | passed|
| vf_smoke | test_vf_jumbo_frames | n/a |
| virtio_smoke| test_virtio_loopback | passed|
| virtio_smoke| test_virtio_pvp | passed|
+-------------+---------------------------+-------+
* Environment:
OS : Ubuntu 20.04.5 LTS
Kernel : 5.13.0-30-generic
GCC : 9.4.0-1ubuntu1~20.04.1
NIC : Ethernet Controller XL710 for 40GbE QSFP+
Target : x86_64-native-linuxapp-gcc
TestPlan:
pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test_plan.rst
vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test_plan.rst
asan_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/asan_smoke_test_plan.rst
TestSuite:
pf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_pf_smoke.py
vf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_vf_smoke.py
virtio_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_virtio_smoke.py
asan_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_asan_smoke.py
DPDK STV team
next reply other threads:[~2022-11-27 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 11:16 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-27 10:47 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='510f81$l6m1nh@fmsmga004-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=chenyux.huang@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=daxuex.gao@intel.com \
--cc=lijuan.tu@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).