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| pw136858-136866 [PATCH] [v2,10/10] net/mlx5/hws: typo fix
Date: Sat, 17 Feb 2024 22:31:47 -0800 (PST)	[thread overview]
Message-ID: <65d1a453.630a0220.31eb6.7330SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Itamar Gozlan <igozlan@nvidia.com>
Date: Sunday, February 18 2024 05:11:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:25e981ab82d28bdc6010f033efc2fdcc35fc2b53

136858-136866 --> 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-83-generic aarch64
Compiler: gcc 9.4
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/29176/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-18  6:31 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18  6:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-18 10:12 dpdklab
2024-02-18 10:03 dpdklab
2024-02-18  9:44 dpdklab
2024-02-18  9:28 dpdklab
2024-02-18  9:21 dpdklab
2024-02-18  7:51 dpdklab
2024-02-18  7:36 dpdklab
2024-02-18  7:32 dpdklab
2024-02-18  7:32 dpdklab
2024-02-18  7:29 dpdklab
2024-02-18  7:28 dpdklab
2024-02-18  7:27 dpdklab
2024-02-18  7:26 dpdklab
2024-02-18  7:25 dpdklab
2024-02-18  7:25 dpdklab
2024-02-18  7:25 dpdklab
2024-02-18  7:23 dpdklab
2024-02-18  7:22 dpdklab
2024-02-18  7:20 dpdklab
2024-02-18  7:19 dpdklab
2024-02-18  7:18 dpdklab
2024-02-18  7:16 dpdklab
2024-02-18  7:15 dpdklab
2024-02-18  7:12 dpdklab
2024-02-18  7:10 dpdklab
2024-02-18  7:09 dpdklab
2024-02-18  7:06 dpdklab
2024-02-18  7:03 dpdklab
2024-02-18  7:03 dpdklab
2024-02-18  7:02 dpdklab
2024-02-18  7:01 dpdklab
2024-02-18  7:01 dpdklab
2024-02-18  7:00 dpdklab
2024-02-18  6:59 dpdklab
2024-02-18  6:59 dpdklab
2024-02-18  6:58 dpdklab
2024-02-18  6:57 dpdklab
2024-02-18  6:56 dpdklab
2024-02-18  6:55 dpdklab
2024-02-18  6:52 dpdklab
2024-02-18  6:51 dpdklab
2024-02-18  6:51 dpdklab
2024-02-18  6:50 dpdklab
2024-02-18  6:47 dpdklab
2024-02-18  6:46 dpdklab
2024-02-18  6:45 dpdklab
2024-02-18  6:44 dpdklab
2024-02-18  6:43 dpdklab
2024-02-18  6:43 dpdklab
2024-02-18  6:39 dpdklab
2024-02-18  6:39 dpdklab
2024-02-18  6:38 dpdklab
2024-02-18  6:38 dpdklab
2024-02-18  6:38 dpdklab
2024-02-18  6:37 dpdklab
2024-02-18  6:36 dpdklab
2024-02-18  6:35 dpdklab
2024-02-18  6:33 dpdklab
2024-02-18  6:33 dpdklab
2024-02-18  6:33 dpdklab
2024-02-18  6:33 dpdklab
2024-02-18  6:33 dpdklab
2024-02-18  6:32 dpdklab
2024-02-18  6:30 dpdklab
2024-02-18  6:30 dpdklab
2024-02-18  6:29 dpdklab
2024-02-18  6:29 dpdklab
2024-02-18  6:24 dpdklab
2024-02-18  6:22 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=65d1a453.630a0220.31eb6.7330SMTPIN_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).