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| pw153490-153489 [PATCH] [v2,2/2] lib/lpm: enable lpm to be
Date: Fri, 16 May 2025 13:12:11 -0700 (PDT)	[thread overview]
Message-ID: <68279c1b.170a0220.bb718.42bfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1747417002-28419-3-git-send-email-andremue@linux.microsoft.com>

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

_Functional Testing PASS_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Friday, May 16 2025 17:36:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:117e86c4b96ed761e9a7ab766261208fe81bf5ca

153490-153489 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#226309

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-16 20:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1747417002-28419-3-git-send-email-andremue@linux.microsoft.com>
2025-05-16 17:09 ` |SUCCESS| pw153490-153489 [PATCH v2 2/2] lib/lpm: enable lpm to be compiled with MSVC qemudev
2025-05-16 17:13 ` qemudev
2025-05-16 17:38 ` |SUCCESS| pw153489 " checkpatch
2025-05-16 18:44 ` 0-day Robot
2025-05-16 20:12 ` dpdklab [this message]
2025-05-16 20:20 ` |SUCCESS| pw153490-153489 [PATCH] [v2,2/2] lib/lpm: enable lpm to be dpdklab
2025-05-16 20:20 ` dpdklab
2025-05-16 20:23 ` dpdklab
2025-05-16 20:23 ` dpdklab
2025-05-16 20:24 ` |PENDING| " dpdklab
2025-05-16 20:26 ` dpdklab
2025-05-16 20:27 ` |SUCCESS| " dpdklab
2025-05-16 20:40 ` dpdklab
2025-05-16 20:40 ` dpdklab
2025-05-16 20:52 ` dpdklab
2025-05-16 21:04 ` dpdklab
2025-05-16 21:05 ` dpdklab
2025-05-16 21:13 ` dpdklab
2025-05-16 21:19 ` dpdklab
2025-05-16 21:20 ` dpdklab
2025-05-16 21:20 ` dpdklab
2025-05-16 21:21 ` dpdklab
2025-05-16 23:26 ` dpdklab
2025-05-17  0:59 ` 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=68279c1b.170a0220.bb718.42bfSMTPIN_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).