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| pw137503 [PATCH] [v2] ethdev: add Linux ethtool link mode
Date: Sun, 03 Mar 2024 08:40:24 -0800 (PST)	[thread overview]
Message-ID: <65e4a7f8.050a0220.716fc.bd55SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229154343.1752555-1-thomas@monjalon.net>

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

_Functional Testing PASS_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Thursday, February 29 2024 15:42:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f60df26faa3c90fc66d356e16347acd046971441

137503 --> 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/29341/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-03 16:40 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240229154343.1752555-1-thomas@monjalon.net>
2024-02-29 15:21 ` |SUCCESS| pw137503 [PATCH v2] ethdev: add Linux ethtool link mode conversion qemudev
2024-02-29 15:25 ` qemudev
2024-02-29 15:45 ` checkpatch
2024-02-29 16:44 ` 0-day Robot
2024-02-29 19:15 ` |SUCCESS| pw137503 [PATCH] [v2] ethdev: add Linux ethtool link mode dpdklab
2024-02-29 19:19 ` dpdklab
2024-02-29 19:22 ` dpdklab
2024-02-29 19:23 ` dpdklab
2024-02-29 19:35 ` dpdklab
2024-02-29 19:37 ` dpdklab
2024-02-29 19:38 ` dpdklab
2024-02-29 19:48 ` dpdklab
2024-02-29 19:51 ` dpdklab
2024-02-29 19:51 ` dpdklab
2024-02-29 19:52 ` dpdklab
2024-02-29 19:53 ` dpdklab
2024-02-29 19:56 ` dpdklab
2024-02-29 19:59 ` dpdklab
2024-02-29 20:01 ` dpdklab
2024-02-29 20:02 ` dpdklab
2024-02-29 20:03 ` dpdklab
2024-02-29 22:52 ` dpdklab
2024-02-29 22:52 ` dpdklab
2024-02-29 22:52 ` dpdklab
2024-02-29 22:53 ` dpdklab
2024-02-29 23:02 ` dpdklab
2024-02-29 23:03 ` dpdklab
2024-02-29 23:03 ` dpdklab
2024-02-29 23:04 ` dpdklab
2024-02-29 23:04 ` dpdklab
2024-02-29 23:05 ` dpdklab
2024-02-29 23:05 ` dpdklab
2024-02-29 23:07 ` dpdklab
2024-02-29 23:07 ` dpdklab
2024-02-29 23:08 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:10 ` dpdklab
2024-02-29 23:10 ` dpdklab
2024-02-29 23:10 ` dpdklab
2024-02-29 23:11 ` dpdklab
2024-02-29 23:12 ` dpdklab
2024-02-29 23:12 ` dpdklab
2024-02-29 23:12 ` dpdklab
2024-02-29 23:13 ` dpdklab
2024-02-29 23:13 ` dpdklab
2024-02-29 23:13 ` dpdklab
2024-02-29 23:14 ` dpdklab
2024-02-29 23:14 ` dpdklab
2024-02-29 23:14 ` dpdklab
2024-02-29 23:19 ` dpdklab
2024-02-29 23:19 ` dpdklab
2024-02-29 23:20 ` dpdklab
2024-02-29 23:20 ` dpdklab
2024-02-29 23:33 ` dpdklab
2024-02-29 23:36 ` dpdklab
2024-02-29 23:40 ` dpdklab
2024-02-29 23:59 ` dpdklab
2024-03-01  0:00 ` dpdklab
2024-03-01  0:34 ` dpdklab
2024-03-01  6:34 ` dpdklab
2024-03-01  9:59 ` dpdklab
2024-03-01 10:05 ` dpdklab
2024-03-01 10:09 ` dpdklab
2024-03-01 10:14 ` dpdklab
2024-03-02 10:22 ` dpdklab
2024-03-03 16:07 ` dpdklab
2024-03-03 16:40 ` dpdklab [this message]
2024-03-03 17:12 ` 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=65e4a7f8.050a0220.716fc.bd55SMTPIN_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).