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| pw153434 [PATCH] net/mlx5: fix mark action value in shared
Date: Wed, 14 May 2025 01:35:37 -0700 (PDT)	[thread overview]
Message-ID: <682455d9.050a0220.2241ff.6cf4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250514075018.67370-1-getelson@nvidia.com>

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

_Functional Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wednesday, May 14 2025 07:50:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0c02b2799a521c45ed72c3f2f011b76d994ebc6a

153434 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#225690

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

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-14  8:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250514075018.67370-1-getelson@nvidia.com>
2025-05-14  7:17 ` |SUCCESS| pw153434 [PATCH] net/mlx5: fix mark action value in shared Rx queue setup qemudev
2025-05-14  7:21 ` qemudev
2025-05-14  7:51 ` checkpatch
2025-05-14  8:35 ` dpdklab [this message]
2025-05-14  8:35 ` |PENDING| pw153434 [PATCH] net/mlx5: fix mark action value in shared dpdklab
2025-05-14  8:39 ` |SUCCESS| " dpdklab
2025-05-14  8:41 ` |PENDING| " dpdklab
2025-05-14  8:43 ` |SUCCESS| pw153434 [PATCH] net/mlx5: fix mark action value in shared Rx queue setup 0-day Robot
2025-05-14  8:44 ` |SUCCESS| pw153434 [PATCH] net/mlx5: fix mark action value in shared dpdklab
2025-05-14  8:45 ` dpdklab
2025-05-14  8:46 ` dpdklab
2025-05-14  8:48 ` dpdklab
2025-05-14  8:48 ` |PENDING| " dpdklab
2025-05-14  8:49 ` |SUCCESS| " dpdklab
2025-05-14  8:57 ` dpdklab
2025-05-14  8:59 ` |PENDING| " dpdklab
2025-05-14  9:01 ` |SUCCESS| " dpdklab
2025-05-14  9:10 ` dpdklab
2025-05-14  9:23 ` dpdklab
2025-05-14  9:32 ` dpdklab
2025-05-14  9:32 ` dpdklab
2025-05-14  9:37 ` dpdklab
2025-05-14  9:52 ` dpdklab
2025-05-14 12:03 ` 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=682455d9.050a0220.2241ff.6cf4SMTPIN_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).