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| pw156831-156833 [PATCH] [v3,4/4] net/cpfl: add cpchnl get
Date: Fri, 26 Sep 2025 01:41:59 -0700 (PDT) [thread overview]
Message-ID: <68d651d7.050a0220.3486ae.9f44SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250923125455.1484992-5-praveen.shetty@intel.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/156833
_Functional Testing PASS RETEST #1_
Submitter: Shetty, Praveen <praveen.shetty@intel.com>
Date: Tuesday, September 23 2025 12:54:55
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: master
CommitID:4159ea62922ce41566c7bab44655ad78bee85458
156831-156833 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#246494
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 |
+----------------+--------+
| dynamic_queue | PASS |
+----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34121/
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-26 8:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250923125455.1484992-5-praveen.shetty@intel.com>
2025-09-23 8:59 ` |SUCCESS| pw156831-156833 [PATCH v3 4/4] net/cpfl: add cpchnl get vport info support qemudev
2025-09-23 9:04 ` qemudev
2025-09-23 9:31 ` |SUCCESS| pw156833 " checkpatch
2025-09-23 10:00 ` |PENDING| pw156831-156833 [PATCH] [v3,4/4] net/cpfl: add cpchnl get dpdklab
2025-09-23 10:02 ` |SUCCESS| " dpdklab
2025-09-23 10:07 ` dpdklab
2025-09-23 10:07 ` |PENDING| " dpdklab
2025-09-23 10:11 ` dpdklab
2025-09-23 10:20 ` |SUCCESS| " dpdklab
2025-09-23 10:22 ` dpdklab
2025-09-23 10:23 ` |PENDING| " dpdklab
2025-09-23 10:24 ` |FAILURE| " dpdklab
2025-09-23 10:24 ` |SUCCESS| " dpdklab
2025-09-23 10:30 ` dpdklab
2025-09-23 10:31 ` dpdklab
2025-09-23 10:39 ` dpdklab
2025-09-23 10:42 ` dpdklab
2025-09-23 10:42 ` dpdklab
2025-09-23 10:43 ` dpdklab
2025-09-23 10:44 ` dpdklab
2025-09-23 11:22 ` |SUCCESS| pw156833 [PATCH v3 4/4] net/cpfl: add cpchnl get vport info support 0-day Robot
2025-09-23 11:22 ` 0-day Robot
2025-09-23 13:12 ` |SUCCESS| pw156831-156833 [PATCH] [v3,4/4] net/cpfl: add cpchnl get dpdklab
2025-09-23 13:19 ` dpdklab
2025-09-26 8:32 ` dpdklab
2025-09-26 8:32 ` dpdklab
2025-09-26 8:41 ` dpdklab
2025-09-26 8:41 ` dpdklab [this message]
2025-09-26 8:46 ` dpdklab
2025-09-26 8:48 ` dpdklab
2025-09-26 8:54 ` dpdklab
2025-09-26 9:05 ` dpdklab
2025-09-26 9:20 ` dpdklab
2025-09-26 22:55 ` dpdklab
2025-09-27 6:58 ` 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=68d651d7.050a0220.3486ae.9f44SMTPIN_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).