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| pw140290 [PATCH] doc: add firmware update links in mlx5 gu
Date: Thu, 23 May 2024 05:58:18 -0700 (PDT)	[thread overview]
Message-ID: <664f3d6a.050a0220.8ee3c.4735SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240523112850.1446671-1-thomas@monjalon.net>

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

_Functional Testing PASS_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Thursday, May 23 2024 11:28:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:58242360b798ccd45190fc9bc68292f26b7c4385

140290 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
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


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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-23 12:58 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240523112850.1446671-1-thomas@monjalon.net>
2024-05-23 11:02 ` |SUCCESS| pw140290 [PATCH] doc: add firmware update links in mlx5 guide qemudev
2024-05-23 11:07 ` qemudev
2024-05-23 11:30 ` checkpatch
2024-05-23 12:21 ` |SUCCESS| pw140290 [PATCH] doc: add firmware update links in mlx5 gu dpdklab
2024-05-23 12:22 ` dpdklab
2024-05-23 12:24 ` |SUCCESS| pw140290 [PATCH] doc: add firmware update links in mlx5 guide 0-day Robot
2024-05-23 12:25 ` |SUCCESS| pw140290 [PATCH] doc: add firmware update links in mlx5 gu dpdklab
2024-05-23 12:26 ` dpdklab
2024-05-23 12:26 ` dpdklab
2024-05-23 12:26 ` dpdklab
2024-05-23 12:28 ` dpdklab
2024-05-23 12:29 ` dpdklab
2024-05-23 12:29 ` dpdklab
2024-05-23 12:32 ` dpdklab
2024-05-23 12:33 ` dpdklab
2024-05-23 12:34 ` dpdklab
2024-05-23 12:39 ` dpdklab
2024-05-23 12:42 ` dpdklab
2024-05-23 12:42 ` dpdklab
2024-05-23 12:42 ` dpdklab
2024-05-23 12:43 ` dpdklab
2024-05-23 12:43 ` dpdklab
2024-05-23 12:44 ` dpdklab
2024-05-23 12:44 ` dpdklab
2024-05-23 12:44 ` dpdklab
2024-05-23 12:45 ` dpdklab
2024-05-23 12:45 ` dpdklab
2024-05-23 12:48 ` dpdklab
2024-05-23 12:48 ` dpdklab
2024-05-23 12:48 ` dpdklab
2024-05-23 12:49 ` dpdklab
2024-05-23 12:49 ` dpdklab
2024-05-23 12:50 ` dpdklab
2024-05-23 12:50 ` dpdklab
2024-05-23 12:50 ` dpdklab
2024-05-23 12:51 ` dpdklab
2024-05-23 12:51 ` dpdklab
2024-05-23 12:51 ` dpdklab
2024-05-23 12:52 ` dpdklab
2024-05-23 12:52 ` dpdklab
2024-05-23 12:54 ` dpdklab
2024-05-23 12:54 ` dpdklab
2024-05-23 12:55 ` dpdklab
2024-05-23 12:55 ` dpdklab
2024-05-23 12:56 ` dpdklab
2024-05-23 12:56 ` dpdklab
2024-05-23 12:57 ` dpdklab
2024-05-23 12:57 ` dpdklab
2024-05-23 12:57 ` dpdklab
2024-05-23 12:57 ` dpdklab
2024-05-23 12:58 ` dpdklab
2024-05-23 12:58 ` dpdklab [this message]
2024-05-23 12:58 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:02 ` dpdklab
2024-05-23 13:02 ` dpdklab
2024-05-23 13:03 ` dpdklab
2024-05-23 13:04 ` dpdklab
2024-05-23 13:04 ` dpdklab
2024-05-23 13:05 ` dpdklab
2024-05-23 13:05 ` dpdklab
2024-05-23 13:05 ` dpdklab
2024-05-23 13:06 ` dpdklab
2024-05-23 13:06 ` dpdklab
2024-05-23 13:09 ` dpdklab
2024-05-23 13:10 ` dpdklab
2024-05-23 13:12 ` dpdklab
2024-05-23 13:13 ` dpdklab
2024-05-23 13:16 ` dpdklab
2024-05-23 13:20 ` dpdklab
2024-05-23 13:21 ` dpdklab
2024-05-23 13:32 ` dpdklab
2024-05-23 13:53 ` dpdklab
2024-05-23 14:07 ` dpdklab
2024-05-23 14:08 ` dpdklab
2024-05-23 14:43 ` dpdklab
2024-05-23 15:44 ` 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=664f3d6a.050a0220.8ee3c.4735SMTPIN_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).