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| pw152160 [PATCH] config: move existing code that is common
Date: Mon, 03 Mar 2025 15:39:25 -0800 (PST)	[thread overview]
Message-ID: <67c63dad.050a0220.2e640b.f81bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1740757940-10253-1-git-send-email-andremue@linux.microsoft.com>

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

_Functional Testing PASS_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Friday, February 28 2025 15:52:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fab31a03ba98e7457284df95dd9eef2223a4ccaa

152160 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#215518

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  |
+----------------+--------+
| dynamic_queue  |  PASS  |
+----------------+--------+
| rxtx_callbacks |  PASS  |
+----------------+--------+


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32718/

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2025-03-03 23:39 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1740757940-10253-1-git-send-email-andremue@linux.microsoft.com>
2025-02-28 15:21 ` |SUCCESS| pw152160 [PATCH] config: move existing code that is common to the top qemudev
2025-02-28 15:26 ` qemudev
2025-02-28 15:53 ` checkpatch
2025-02-28 17:04 ` 0-day Robot
2025-03-01  7:56 ` |SUCCESS| pw152160 [PATCH] config: move existing code that is common dpdklab
2025-03-01  7:58 ` dpdklab
2025-03-01  8:14 ` dpdklab
2025-03-01  8:41 ` dpdklab
2025-03-01  9:05 ` dpdklab
2025-03-01  9:14 ` dpdklab
2025-03-01  9:16 ` dpdklab
2025-03-01  9:30 ` dpdklab
2025-03-01  9:31 ` dpdklab
2025-03-01  9:32 ` dpdklab
2025-03-01  9:36 ` dpdklab
2025-03-01  9:53 ` dpdklab
2025-03-01  9:55 ` dpdklab
2025-03-01 10:26 ` dpdklab
2025-03-01 10:47 ` dpdklab
2025-03-01 10:56 ` dpdklab
2025-03-01 10:57 ` dpdklab
2025-03-01 11:43 ` |PENDING| " dpdklab
2025-03-01 12:35 ` |SUCCESS| " dpdklab
2025-03-01 12:35 ` dpdklab
2025-03-01 13:11 ` |PENDING| " dpdklab
2025-03-01 13:18 ` |SUCCESS| " dpdklab
2025-03-01 13:19 ` dpdklab
2025-03-01 14:04 ` |PENDING| " dpdklab
2025-03-01 14:22 ` |SUCCESS| " dpdklab
2025-03-01 14:42 ` dpdklab
2025-03-01 14:58 ` |PENDING| " dpdklab
2025-03-01 15:01 ` |SUCCESS| " dpdklab
2025-03-01 15:08 ` dpdklab
2025-03-01 15:37 ` dpdklab
2025-03-01 15:37 ` dpdklab
2025-03-01 15:39 ` dpdklab
2025-03-01 17:19 ` dpdklab
2025-03-01 20:36 ` dpdklab
2025-03-01 21:22 ` dpdklab
2025-03-02  0:42 ` dpdklab
2025-03-02  0:54 ` dpdklab
2025-03-02  4:53 ` dpdklab
2025-03-02  4:54 ` dpdklab
2025-03-02  4:57 ` dpdklab
2025-03-02  4:58 ` dpdklab
2025-03-02 16:21 ` dpdklab
2025-03-02 16:52 ` dpdklab
2025-03-03 23:31 ` dpdklab
2025-03-03 23:39 ` dpdklab [this message]

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=67c63dad.050a0220.2e640b.f81bSMTPIN_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).