From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155011 [PATCH] app/testpmd: allow multiple cmdline-file
Date: Mon, 14 Jul 2025 14:49:13 -0700 (PDT) [thread overview]
Message-ID: <68757b59.050a0220.143a27.140dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250704140551.4151993-1-bruce.richardson@intel.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/155011
_Functional Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, July 04 2025 14:05:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ba982f9a1ca9b96ed0394b764f1523d482e963a2
155011 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#236148
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+----------------+--------+
| Test Suite | Result |
+================+========+
| cmdline | PASS |
+----------------+--------+
| rxtx_callbacks | PASS |
+----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33594/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-07-14 21:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250704140551.4151993-1-bruce.richardson@intel.com>
2025-07-04 13:31 ` |SUCCESS| pw155011 [PATCH] app/testpmd: allow multiple cmdline-file parameters qemudev
2025-07-04 13:36 ` qemudev
2025-07-04 14:05 ` checkpatch
2025-07-04 15:23 ` 0-day Robot
2025-07-09 15:27 ` |FAILURE| " dpdklab
2025-07-09 16:48 ` dpdklab
2025-07-09 22:12 ` |SUCCESS| pw155011 [PATCH] app/testpmd: allow multiple cmdline-file dpdklab
2025-07-09 22:20 ` dpdklab
2025-07-09 22:28 ` |PENDING| " dpdklab
2025-07-09 22:39 ` |SUCCESS| " dpdklab
2025-07-09 22:46 ` dpdklab
2025-07-09 23:14 ` dpdklab
2025-07-09 23:16 ` dpdklab
2025-07-10 0:04 ` dpdklab
2025-07-10 0:06 ` dpdklab
2025-07-10 0:10 ` dpdklab
2025-07-10 0:13 ` |WARNING| " dpdklab
2025-07-10 0:13 ` dpdklab
2025-07-10 0:14 ` dpdklab
2025-07-10 0:21 ` |SUCCESS| " dpdklab
2025-07-10 0:23 ` |WARNING| " dpdklab
2025-07-10 2:30 ` |SUCCESS| " dpdklab
2025-07-10 2:31 ` dpdklab
2025-07-10 4:13 ` |WARNING| " dpdklab
2025-07-10 5:09 ` dpdklab
2025-07-10 9:30 ` |SUCCESS| " dpdklab
2025-07-10 9:36 ` dpdklab
2025-07-10 14:39 ` |WARNING| " dpdklab
2025-07-10 16:19 ` |SUCCESS| " dpdklab
2025-07-14 21:49 ` dpdklab [this message]
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=68757b59.050a0220.143a27.140dSMTPIN_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).