From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw156850 [PATCH] examples/l2fwd-cat: check compatibility o
Date: Tue, 23 Sep 2025 10:46:13 -0700 (PDT) [thread overview]
Message-ID: <68d2dce5.050a0220.46195.3cfdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250923165830.527416-1-bruce.richardson@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/156850
_Functional Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, September 23 2025 16:58:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0e03ab647d07cd985a7cac36cefff5195cc3a07d
156850 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#245915
Test environment and result as below:
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 |
+--------------------+--------+
| promisc_support | PASS |
+--------------------+--------+
| uni_pkt | PASS |
+--------------------+--------+
| dynamic_config | PASS |
+--------------------+--------+
| dynamic_queue_conf | PASS |
+--------------------+--------+
| hello_world | PASS |
+--------------------+--------+
| l2fwd | PASS |
+--------------------+--------+
| softnic | PASS |
+--------------------+--------+
| vlan | 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/34127/
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-09-23 17:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250923165830.527416-1-bruce.richardson@intel.com>
2025-09-23 16:23 ` |SUCCESS| pw156850 [PATCH] examples/l2fwd-cat: check compatibility of dependency lib qemudev
2025-09-23 16:28 ` qemudev
2025-09-23 16:57 ` checkpatch
2025-09-23 17:23 ` |PENDING| pw156850 [PATCH] examples/l2fwd-cat: check compatibility o dpdklab
2025-09-23 17:25 ` |SUCCESS| " dpdklab
2025-09-23 17:29 ` dpdklab
2025-09-23 17:38 ` |PENDING| " dpdklab
2025-09-23 17:43 ` dpdklab
2025-09-23 17:45 ` |SUCCESS| " dpdklab
2025-09-23 17:46 ` dpdklab [this message]
2025-09-23 17:51 ` dpdklab
2025-09-23 17:54 ` |FAILURE| " dpdklab
2025-09-23 17:54 ` |SUCCESS| " dpdklab
2025-09-23 18:14 ` dpdklab
2025-09-23 18:17 ` dpdklab
2025-09-23 18:18 ` dpdklab
2025-09-23 18:19 ` dpdklab
2025-09-23 18:29 ` dpdklab
2025-09-23 18:37 ` dpdklab
2025-09-23 18:39 ` |FAILURE| pw156850 [PATCH] examples/l2fwd-cat: check compatibility of dependency lib 0-day Robot
2025-09-23 18:50 ` |SUCCESS| pw156850 [PATCH] examples/l2fwd-cat: check compatibility o dpdklab
2025-09-23 18:57 ` dpdklab
2025-09-24 1:07 ` dpdklab
2025-09-24 2:54 ` 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=68d2dce5.050a0220.46195.3cfdSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).