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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| pw158180-158181 [PATCH] [2/2] net/mlx5: support PF represe
Date: Tue, 28 Oct 2025 04:19:29 -0700 (PDT)	[thread overview]
Message-ID: <6900a6c1.050a0220.2b76c0.bb93SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251028095831.53669-2-getelson@nvidia.com>

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

_Functional Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, October 28 2025 09:58:30 
DPDK git baseline: Repo:dpdk-next-net
  Branch: master
  CommitID:11a6a4b1f19140ac3a57ace844be3cba00c39eaa

158180-158181 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#251673

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-10-28 11:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251028095831.53669-2-getelson@nvidia.com>
2025-10-28  9:34 ` |SUCCESS| pw158180-158181 [PATCH 2/2] net/mlx5: support PF representor suppresion in multi-port E-Switch qemudev
2025-10-28  9:39 ` |FAILURE| " qemudev
2025-10-28 10:00 ` |WARNING| pw158181 " checkpatch
2025-10-28 11:13 ` |SUCCESS| pw158180-158181 [PATCH] [2/2] net/mlx5: support PF represe dpdklab
2025-10-28 11:19 ` dpdklab [this message]
2025-10-28 11:20 ` |PENDING| " dpdklab
2025-10-28 11:22 ` |SUCCESS| " dpdklab
2025-10-28 11:22 ` |FAILURE| pw158181 [PATCH 2/2] net/mlx5: support PF representor suppresion in multi-port E-Switch 0-day Robot
2025-10-28 11:29 ` |SUCCESS| pw158180-158181 [PATCH] [2/2] net/mlx5: support PF represe dpdklab
2025-10-28 12:10 ` dpdklab
2025-10-28 12:32 ` dpdklab
2025-10-28 12:49 ` |PENDING| " dpdklab
2025-10-28 13:11 ` dpdklab
2025-10-28 13:16 ` |SUCCESS| " dpdklab
2025-10-28 13:16 ` dpdklab
2025-10-28 13:56 ` |WARNING| " dpdklab
2025-10-28 14:52 ` |FAILURE| " dpdklab
2025-10-28 15:53 ` |WARNING| " dpdklab
2025-10-28 16:06 ` dpdklab
2025-10-28 16:10 ` |FAILURE| " dpdklab
2025-10-28 16:57 ` |SUCCESS| " dpdklab
2025-10-28 17:18 ` |WARNING| " dpdklab
2025-10-28 17:31 ` |FAILURE| " dpdklab
2025-10-28 17:44 ` |SUCCESS| " dpdklab
2025-10-28 18:05 ` |FAILURE| " dpdklab
2025-10-28 18:25 ` |SUCCESS| " dpdklab
2025-10-28 18:49 ` |FAILURE| " dpdklab
2025-10-28 20:58 ` dpdklab
2025-10-28 21:02 ` |WARNING| " dpdklab
2025-10-28 21: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=6900a6c1.050a0220.2b76c0.bb93SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).