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| pw152041-152044 [PATCH] [V1,4/4] net/mlx5/hws: allow diffe
Date: Tue, 25 Feb 2025 16:28:09 -0800 (PST)	[thread overview]
Message-ID: <67be6019.c80a0220.05ec.7e41SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250225120213.2968616-4-ophirmu@nvidia.com>

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

_Functional Testing PASS_

Submitter: Ophir Munk <ophirmu@nvidia.com>
Date: Tuesday, February 25 2025 12:02:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:61fc05f1c6a079c0b25b27d1668450134a784d56

152041-152044 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#214394

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-02-26  0:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250225120213.2968616-4-ophirmu@nvidia.com>
2025-02-25 11:40 ` |SUCCESS| pw152041-152044 [PATCH V1 4/4] net/mlx5/hws: allow different types in miss validation qemudev
2025-02-25 11:45 ` qemudev
2025-02-25 12:05 ` |SUCCESS| pw152044 " checkpatch
2025-02-25 13:04 ` |FAILURE| " 0-day Robot
2025-02-25 16:11 ` |SUCCESS| pw152041-152044 [PATCH] [V1,4/4] net/mlx5/hws: allow diffe dpdklab
2025-02-25 16:11 ` dpdklab
2025-02-25 16:20 ` dpdklab
2025-02-25 16:25 ` dpdklab
2025-02-25 16:33 ` dpdklab
2025-02-25 16:46 ` dpdklab
2025-02-25 17:08 ` |PENDING| " dpdklab
2025-02-25 17:37 ` |FAILURE| " dpdklab
2025-02-25 17:39 ` |PENDING| " dpdklab
2025-02-25 18:07 ` |SUCCESS| " dpdklab
2025-02-25 18:12 ` |WARNING| " dpdklab
2025-02-25 18:21 ` dpdklab
2025-02-25 19:11 ` dpdklab
2025-02-25 19:17 ` |FAILURE| " dpdklab
2025-02-25 19:17 ` dpdklab
2025-02-25 19:17 ` dpdklab
2025-02-25 19:45 ` dpdklab
2025-02-25 20:18 ` dpdklab
2025-02-26  0:28 ` dpdklab [this message]
2025-02-26  8:09 ` 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=67be6019.c80a0220.05ec.7e41SMTPIN_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).