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| pw156712-156714 [PATCH] [3/3] member: hide internal macro
Date: Thu, 18 Sep 2025 01:11:54 -0700 (PDT)	[thread overview]
Message-ID: <68cbbeca.170a0220.edc0c.785eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250918073135.1273767-4-thomas@monjalon.net>

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

_Functional Testing PASS_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Thursday, September 18 2025 07:28:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6e6cc1dc3548fc862cea377c98d7feef1a335468

156712-156714 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#245183

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-09-18  8:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250918073135.1273767-4-thomas@monjalon.net>
2025-09-18  6:57 ` |SUCCESS| pw156712-156714 [PATCH 3/3] " qemudev
2025-09-18  7:02 ` qemudev
2025-09-18  7:30 ` |SUCCESS| pw156714 " checkpatch
2025-09-18  8:07 ` |SUCCESS| pw156712-156714 [PATCH] [3/3] " dpdklab
2025-09-18  8:09 ` |PENDING| " dpdklab
2025-09-18  8:11 ` dpdklab [this message]
2025-09-18  8:16 ` |SUCCESS| " dpdklab
2025-09-18  8:19 ` |PENDING| " dpdklab
2025-09-18  8:27 ` |SUCCESS| " dpdklab
2025-09-18  8:30 ` |FAILURE| pw156714 [PATCH 3/3] " 0-day Robot
2025-09-18  8:34 ` |PENDING| pw156712-156714 [PATCH] [3/3] " dpdklab
2025-09-18  8:38 ` |SUCCESS| " dpdklab
2025-09-18  8:38 ` dpdklab
2025-09-18  8:39 ` |PENDING| " dpdklab
2025-09-18  8:54 ` |SUCCESS| " dpdklab
2025-09-18  8:59 ` dpdklab
2025-09-18  9:06 ` dpdklab
2025-09-18 10:08 ` dpdklab
2025-09-18 10:09 ` dpdklab
2025-09-18 10:20 ` dpdklab
2025-09-18 10:26 ` dpdklab
2025-09-18 10:59 ` dpdklab
2025-09-18 11:22 ` dpdklab
2025-09-18 11:31 ` dpdklab
2025-09-18 11:32 ` dpdklab
2025-09-18 12:35 ` 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=68cbbeca.170a0220.edc0c.785eSMTPIN_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).