From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Bruce Richardson <bruce.richardson@intel.com>
Subject: |SUCCESS| pw158542 [PATCH] net/ice: fix statistics read error
Date: Fri, 07 Nov 2025 00:11:07 -0800 (PST) [thread overview]
Message-ID: <690da99b.050a0220.268c54.4ffaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251107074338.957352-1-zhichaox.zeng@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/158542
_Functional Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Friday, November 07 2025 07:43:38
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: master
CommitID:1655dc989bc95fa85fc76d32912d2e46c0851148
158542 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#253535
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel E810 (Arm Grace Server) 100000 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| blocklist | PASS |
+------------+--------+
| uni_pkt | PASS |
+------------+--------+
Ubuntu 24.04 LTS
Kernel: 6.8.0-44-generic
Compiler: gcc 13.2.0
NIC: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ 40 Mbps
Aggregate Results by Test Suite
+--------------------+--------+
| Test Suite | Result |
+====================+========+
| blocklist | PASS |
+--------------------+--------+
| uni_pkt | PASS |
+--------------------+--------+
| promisc_support | PASS |
+--------------------+--------+
| dynamic_queue_conf | PASS |
+--------------------+--------+
| hello_world | PASS |
+--------------------+--------+
| l2fwd | PASS |
+--------------------+--------+
| softnic | PASS |
+--------------------+--------+
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34504/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-11-07 8:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251107074338.957352-1-zhichaox.zeng@intel.com>
2025-11-07 6:49 ` qemudev
2025-11-07 6:54 ` qemudev
2025-11-07 7:23 ` checkpatch
2025-11-07 7:51 ` |PENDING| " dpdklab
2025-11-07 7:54 ` |SUCCESS| " dpdklab
2025-11-07 7:54 ` |PENDING| " dpdklab
2025-11-07 7:59 ` |SUCCESS| " dpdklab
2025-11-07 8:03 ` |PENDING| " dpdklab
2025-11-07 8:04 ` dpdklab
2025-11-07 8:11 ` dpdklab [this message]
2025-11-07 8:14 ` |SUCCESS| " dpdklab
2025-11-07 8:16 ` dpdklab
2025-11-07 8:16 ` dpdklab
2025-11-07 8:22 ` dpdklab
2025-11-07 8:31 ` dpdklab
2025-11-07 8:35 ` dpdklab
2025-11-07 8:41 ` dpdklab
2025-11-07 8:42 ` dpdklab
2025-11-07 8:46 ` dpdklab
2025-11-07 9:01 ` dpdklab
2025-11-07 9:23 ` dpdklab
2025-11-07 9:47 ` 0-day Robot
2025-11-07 9:47 ` 0-day Robot
2025-11-07 12:47 ` dpdklab
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=690da99b.050a0220.268c54.4ffaSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).