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| pw137413 [PATCH] net/mlx5: add HWS support for matching in
Date: Thu, 29 Feb 2024 14:31:28 -0800 (PST)	[thread overview]
Message-ID: <65e105c0.620a0220.6f055.8e92SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228094056.3107676-1-michaelba@nvidia.com>

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137413

_Functional Testing PASS_

Submitter: Michael Baum <michaelba@nvidia.com>
Date: Wednesday, February 28 2024 09:40:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fba0d7ac2d84dbe0e12b4989198640e14216762b

137413 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29310/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-29 22:31 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240228094056.3107676-1-michaelba@nvidia.com>
2024-02-28  9:17 ` |SUCCESS| pw137413 [PATCH] net/mlx5: add HWS support for matching ingress metadata qemudev
2024-02-28  9:22 ` qemudev
2024-02-28  9:42 ` checkpatch
2024-02-28 12:52 ` |SUCCESS| pw137413 [PATCH] net/mlx5: add HWS support for matching in dpdklab
2024-02-28 12:55 ` dpdklab
2024-02-28 12:59 ` dpdklab
2024-02-28 13:01 ` dpdklab
2024-02-28 13:02 ` dpdklab
2024-02-28 13:02 ` dpdklab
2024-02-28 13:02 ` dpdklab
2024-02-28 13:06 ` dpdklab
2024-02-28 13:06 ` dpdklab
2024-02-28 13:06 ` dpdklab
2024-02-28 13:07 ` dpdklab
2024-02-28 13:09 ` dpdklab
2024-02-28 13:11 ` dpdklab
2024-02-28 13:27 ` dpdklab
2024-02-28 13:37 ` dpdklab
2024-02-28 13:43 ` |FAILURE| " dpdklab
2024-02-28 13:44 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:45 ` |SUCCESS| " dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:46 ` dpdklab
2024-02-28 13:46 ` dpdklab
2024-02-28 13:46 ` dpdklab
2024-02-28 13:46 ` dpdklab
2024-02-28 13:47 ` dpdklab
2024-02-28 13:47 ` dpdklab
2024-02-28 13:47 ` |FAILURE| " dpdklab
2024-02-28 13:47 ` dpdklab
2024-02-28 13:47 ` |SUCCESS| " dpdklab
2024-02-28 13:47 ` |FAILURE| " dpdklab
2024-02-28 13:48 ` |SUCCESS| " dpdklab
2024-02-28 13:48 ` dpdklab
2024-02-28 13:48 ` |FAILURE| " dpdklab
2024-02-28 13:48 ` dpdklab
2024-02-28 13:48 ` dpdklab
2024-02-28 13:48 ` |SUCCESS| " dpdklab
2024-02-28 13:49 ` dpdklab
2024-02-28 13:49 ` dpdklab
2024-02-28 13:49 ` dpdklab
2024-02-28 13:49 ` |FAILURE| " dpdklab
2024-02-28 13:50 ` dpdklab
2024-02-28 13:50 ` dpdklab
2024-02-28 13:50 ` |SUCCESS| " dpdklab
2024-02-28 13:50 ` dpdklab
2024-02-28 13:51 ` |FAILURE| " dpdklab
2024-02-28 13:51 ` |SUCCESS| " dpdklab
2024-02-28 13:51 ` dpdklab
2024-02-28 13:51 ` dpdklab
2024-02-28 13:52 ` |FAILURE| " dpdklab
2024-02-28 13:52 ` |SUCCESS| " dpdklab
2024-02-28 13:52 ` dpdklab
2024-02-28 13:57 ` dpdklab
2024-02-28 13:58 ` dpdklab
2024-02-28 14:08 ` dpdklab
2024-02-28 14:09 ` dpdklab
2024-02-28 14:09 ` dpdklab
2024-02-28 14:09 ` dpdklab
2024-02-28 14:10 ` |FAILURE| " dpdklab
2024-02-28 14:15 ` |SUCCESS| " dpdklab
2024-02-28 14:16 ` dpdklab
2024-02-28 14:33 ` dpdklab
2024-02-28 15:08 ` dpdklab
2024-02-28 17:45 ` dpdklab
2024-02-28 19:39 ` dpdklab
2024-02-28 19:50 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 22:18 ` dpdklab
2024-02-29 22:21 ` dpdklab
2024-02-29 22:27 ` dpdklab
2024-02-29 22:31 ` dpdklab [this message]
2024-03-01 15:57 ` dpdklab
2024-03-01 16:39 ` dpdklab
2024-03-01 17:11 ` 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=65e105c0.620a0220.6f055.8e92SMTPIN_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).