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| pw152191 [PATCH] net/mlx5: fix flow create failure with GE
Date: Mon, 03 Mar 2025 17:59:30 -0800 (PST)	[thread overview]
Message-ID: <67c65e82.050a0220.2c2aef.487aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250303132931.71335-1-mkashani@nvidia.com>

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

_Functional Testing PASS_

Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Monday, March 03 2025 13:29:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cf35973540c8bb4ca5c7d105985a65a3602e5475

152191 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#215784

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

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-04  1:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250303132931.71335-1-mkashani@nvidia.com>
2025-03-03 12:55 ` |SUCCESS| pw152191 [PATCH] net/mlx5: fix flow create failure with GENEVE options match qemudev
2025-03-03 12:59 ` qemudev
2025-03-03 13:31 ` |WARNING| " checkpatch
2025-03-03 13:59 ` |PENDING| pw152191 [PATCH] net/mlx5: fix flow create failure with GE dpdklab
2025-03-03 14:05 ` dpdklab
2025-03-03 14:06 ` dpdklab
2025-03-03 14:13 ` |SUCCESS| " dpdklab
2025-03-03 14:17 ` dpdklab
2025-03-03 14:18 ` |PENDING| " dpdklab
2025-03-03 14:19 ` |SUCCESS| " dpdklab
2025-03-03 14:27 ` dpdklab
2025-03-03 14:30 ` dpdklab
2025-03-03 14:33 ` dpdklab
2025-03-03 14:38 ` dpdklab
2025-03-03 14:40 ` dpdklab
2025-03-03 14:41 ` dpdklab
2025-03-03 14:47 ` dpdklab
2025-03-03 14:58 ` dpdklab
2025-03-03 15:36 ` dpdklab
2025-03-03 16:35 ` dpdklab
2025-03-04  1:59 ` 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=67c65e82.050a0220.2c2aef.487aSMTPIN_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).