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| pw156179-156178 [PATCH] [2/2] examples/l3fwd-power: suppor
Date: Wed, 27 Aug 2025 17:49:55 -0700 (PDT)	[thread overview]
Message-ID: <68afa7b3.050a0220.d47a1.aab9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250827013106.2453922-2-huangdengdui@huawei.com>

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

_Functional Testing PASS_

Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Wednesday, August 27 2025 01:31:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:38543d33bd47fc0ee21f59db80a8763620741879

156179-156178 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#241995

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-08-28  0:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250827013106.2453922-2-huangdengdui@huawei.com>
2025-08-27  1:03 ` |SUCCESS| pw156179-156178 [PATCH 2/2] examples/l3fwd-power: support specify link speed qemudev
2025-08-27  1:07 ` qemudev
2025-08-27  1:29 ` |SUCCESS| pw156178 " checkpatch
2025-08-27  2:47 ` 0-day Robot
2025-08-28  0:40 ` |PENDING| pw156179-156178 [PATCH] [2/2] examples/l3fwd-power: suppor dpdklab
2025-08-28  0:43 ` |SUCCESS| " dpdklab
2025-08-28  0:47 ` dpdklab
2025-08-28  0:49 ` dpdklab [this message]
2025-08-28  1:45 ` dpdklab
2025-08-28  2:54 ` dpdklab
2025-08-28  2:54 ` dpdklab
2025-08-28  3:34 ` dpdklab
2025-08-28  4:42 ` dpdklab
2025-08-28  4:47 ` |PENDING| " dpdklab
2025-08-28  4:52 ` dpdklab
2025-08-28  5:09 ` |SUCCESS| " dpdklab
2025-08-28  5:38 ` dpdklab
2025-08-28  5:41 ` dpdklab
2025-08-28  7:00 ` dpdklab
2025-08-28  7:47 ` dpdklab
2025-08-28 10:09 ` |PENDING| " dpdklab
2025-08-28 10:16 ` |WARNING| " 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=68afa7b3.050a0220.d47a1.aab9SMTPIN_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).