automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw159473 [PATCH] examples/l3fwd: extend NUMA nodes limit b
Date: Fri, 09 Jan 2026 02:33:24 -0800 (PST)	[thread overview]
Message-ID: <6960d974.170a0220.349e88.31d6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251226081719.1120313-1-wangliangxing@hygon.cn>

Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/159473

_Functional Testing PASS_

Submitter: Liangxing Wang <wangliangxing@hygon.cn>
Date: Friday, December 26 2025 08:17:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cd60dcd503b91956f966a1f6d595b35d256ac00f

159473 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#260960

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/34839/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2026-01-09 10:33 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251226081719.1120313-1-wangliangxing@hygon.cn>
2025-12-26  8:17 ` |WARNING| pw159473 [PATCH] examples/l3fwd: extend NUMA nodes limit beyond 8 checkpatch
2025-12-26 10:04 ` |SUCCESS| " qemudev
2025-12-26 10:09 ` qemudev
2025-12-26 12:21 ` 0-day Robot
2025-12-26 12:21 ` 0-day Robot
2026-01-09  9:05 ` |SUCCESS| pw159473 [PATCH] examples/l3fwd: extend NUMA nodes limit b dpdklab
2026-01-09  9:32 ` dpdklab
2026-01-09  9:44 ` dpdklab
2026-01-09  9:44 ` dpdklab
2026-01-09  9:51 ` dpdklab
2026-01-09  9:54 ` dpdklab
2026-01-09 10:02 ` dpdklab
2026-01-09 10:18 ` dpdklab
2026-01-09 10:29 ` dpdklab
2026-01-09 10:30 ` dpdklab
2026-01-09 10:33 ` dpdklab [this message]
2026-01-09 10:41 ` dpdklab
2026-01-09 10:44 ` dpdklab
2026-01-09 10:56 ` dpdklab
2026-01-09 14:42 ` |PENDING| " dpdklab
2026-01-09 15:00 ` dpdklab
2026-01-09 15:55 ` |SUCCESS| " dpdklab
2026-01-09 16:38 ` dpdklab
2026-01-09 17:37 ` dpdklab
2026-01-09 22:44 ` dpdklab
2026-01-09 23:35 ` dpdklab
2026-01-10  1:50 ` dpdklab
2026-01-10  2:05 ` dpdklab
2026-01-10  2:22 ` dpdklab
2026-01-10  2:30 ` dpdklab
2026-01-10  8:32 ` |PENDING| " dpdklab
2026-01-10  8:38 ` |SUCCESS| " dpdklab
2026-01-11  2:34 ` dpdklab
2026-01-11  2:53 ` dpdklab
2026-01-11  3:04 ` dpdklab
2026-01-11  3:26 ` dpdklab
2026-01-11  6:43 ` dpdklab
2026-01-11  7:44 ` 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=6960d974.170a0220.349e88.31d6SMTPIN_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).