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| pw153576-153578 [PATCH] [v2,3/3] dts: add flow validation
Date: Wed, 21 May 2025 13:08:19 -0700 (PDT)	[thread overview]
Message-ID: <682e32b3.050a0220.fb296.317fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250521192629.294265-3-dmarx@iol.unh.edu>

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

_Functional Testing PASS_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Wednesday, May 21 2025 19:26:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1aef42bc97a31906486c9d66b792208948af06f3

153576-153578 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#227050

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

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-21 20:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250521192629.294265-3-dmarx@iol.unh.edu>
2025-05-21 19:01 ` |SUCCESS| pw153576-153578 [PATCH v2 3/3] " qemudev
2025-05-21 19:05 ` qemudev
2025-05-21 19:27 ` |SUCCESS| pw153578 " checkpatch
2025-05-21 20:08 ` dpdklab [this message]
2025-05-21 20:14 ` |SUCCESS| pw153576-153578 [PATCH] [v2,3/3] " dpdklab
2025-05-21 20:19 ` dpdklab
2025-05-21 20:21 ` dpdklab
2025-05-21 20:23 ` dpdklab
2025-05-21 20:26 ` dpdklab
2025-05-21 20:34 ` dpdklab
2025-05-21 20:43 ` |SUCCESS| pw153578 [PATCH v2 3/3] " 0-day Robot
2025-05-21 20:44 ` |SUCCESS| pw153576-153578 [PATCH] [v2,3/3] " dpdklab
2025-05-21 20:48 ` dpdklab
2025-05-21 21:01 ` |PENDING| " dpdklab
2025-05-21 21:15 ` |SUCCESS| " dpdklab
2025-05-21 21:19 ` |PENDING| " dpdklab
2025-05-21 21:48 ` dpdklab
2025-05-21 22:05 ` dpdklab
2025-05-21 22:34 ` |SUCCESS| " dpdklab
2025-05-21 22:49 ` |WARNING| " dpdklab
2025-05-21 22:50 ` dpdklab
2025-05-21 23:09 ` |SUCCESS| " dpdklab
2025-05-21 23:54 ` |WARNING| " dpdklab
2025-05-22  1:06 ` |SUCCESS| " dpdklab
2025-05-22  2:30 ` 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=682e32b3.050a0220.fb296.317fSMTPIN_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).