From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw159400 [PATCH] [v2] examples/ethtool: fix buffer size fo
Date: Fri, 09 Jan 2026 03:46:48 -0800 (PST) [thread overview]
Message-ID: <6960eaa8.170a0220.277c44.a90cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251222083858.1035980-1-shperetz@nvidia.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/159400
_Functional Testing PASS_
Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Monday, December 22 2025 08:38:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cd60dcd503b91956f966a1f6d595b35d256ac00f
159400 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#260986
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/34850/
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:[~2026-01-09 11:46 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251222083858.1035980-1-shperetz@nvidia.com>
2025-12-22 8:38 ` |SUCCESS| pw159400 [PATCH v2] examples/ethtool: fix buffer size for pkt pool name checkpatch
2025-12-22 9:01 ` qemudev
2025-12-22 9:06 ` qemudev
2025-12-22 9:23 ` 0-day Robot
2025-12-22 9:23 ` 0-day Robot
2026-01-09 11:09 ` |SUCCESS| pw159400 [PATCH] [v2] examples/ethtool: fix buffer size fo dpdklab
2026-01-09 11:46 ` dpdklab
2026-01-09 11:46 ` dpdklab [this message]
2026-01-09 11:47 ` dpdklab
2026-01-09 11:48 ` dpdklab
2026-01-09 11:48 ` dpdklab
2026-01-09 11:57 ` dpdklab
2026-01-09 12:05 ` dpdklab
2026-01-09 12:09 ` dpdklab
2026-01-09 12:13 ` dpdklab
2026-01-09 12:32 ` dpdklab
2026-01-09 12:33 ` dpdklab
2026-01-09 12:35 ` dpdklab
2026-01-09 12:36 ` dpdklab
2026-01-09 12:52 ` dpdklab
2026-01-09 12:54 ` dpdklab
2026-01-09 13:04 ` dpdklab
2026-01-09 13:07 ` dpdklab
2026-01-09 15:46 ` |PENDING| " dpdklab
2026-01-09 15:50 ` dpdklab
2026-01-09 16:54 ` |SUCCESS| " dpdklab
2026-01-09 17:19 ` dpdklab
2026-01-10 1:15 ` dpdklab
2026-01-10 2:02 ` dpdklab
2026-01-10 3:12 ` dpdklab
2026-01-10 3:23 ` dpdklab
2026-01-10 3:43 ` dpdklab
2026-01-10 3:51 ` dpdklab
2026-01-10 10:05 ` |PENDING| " dpdklab
2026-01-11 4:03 ` |SUCCESS| " dpdklab
2026-01-11 4:22 ` dpdklab
2026-01-11 4:46 ` dpdklab
2026-01-11 5:04 ` dpdklab
2026-01-11 9:40 ` dpdklab
2026-01-11 10:17 ` dpdklab
2026-01-12 8:17 ` dpdklab
2026-01-12 8:48 ` dpdklab
2026-01-12 9:38 ` |FAILURE| " dpdklab
2026-01-12 15:15 ` 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=6960eaa8.170a0220.277c44.a90cSMTPIN_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).