From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137487 [PATCH] [v1] ethdev: add Linux ethtool link mode
Date: Fri, 01 Mar 2024 00:44:02 -0800 (PST) [thread overview]
Message-ID: <65e19552.170a0220.58b77.1c9dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229123653.1379466-1-thomas@monjalon.net>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137487
_Functional Testing PASS_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Thursday, February 29 2024 12:34:27
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f60df26faa3c90fc66d356e16347acd046971441
137487 --> 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/29334/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-01 8:44 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229123653.1379466-1-thomas@monjalon.net>
2024-02-29 12:14 ` |SUCCESS| pw137487 [PATCH v1] ethdev: add Linux ethtool link mode conversion qemudev
2024-02-29 12:18 ` qemudev
2024-02-29 12:39 ` |WARNING| " checkpatch
2024-02-29 13:25 ` |SUCCESS| " 0-day Robot
2024-02-29 16:18 ` |SUCCESS| pw137487 [PATCH] [v1] ethdev: add Linux ethtool link mode dpdklab
2024-02-29 16:23 ` dpdklab
2024-02-29 16:26 ` dpdklab
2024-02-29 16:34 ` dpdklab
2024-02-29 16:38 ` dpdklab
2024-02-29 16:38 ` dpdklab
2024-02-29 16:39 ` dpdklab
2024-02-29 16:41 ` dpdklab
2024-02-29 16:41 ` dpdklab
2024-02-29 16:44 ` dpdklab
2024-02-29 16:46 ` dpdklab
2024-02-29 16:54 ` dpdklab
2024-02-29 17:02 ` dpdklab
2024-02-29 17:02 ` dpdklab
2024-02-29 17:03 ` dpdklab
2024-02-29 17:03 ` dpdklab
2024-02-29 17:03 ` dpdklab
2024-02-29 17:20 ` dpdklab
2024-02-29 19:22 ` dpdklab
2024-02-29 19:23 ` dpdklab
2024-02-29 19:24 ` dpdklab
2024-02-29 19:24 ` dpdklab
2024-02-29 19:25 ` dpdklab
2024-02-29 19:25 ` dpdklab
2024-02-29 19:29 ` dpdklab
2024-02-29 19:30 ` dpdklab
2024-02-29 19:37 ` dpdklab
2024-02-29 19:38 ` dpdklab
2024-02-29 19:49 ` dpdklab
2024-02-29 19:51 ` dpdklab
2024-02-29 19:52 ` dpdklab
2024-02-29 19:53 ` |FAILURE| " dpdklab
2024-02-29 19:54 ` dpdklab
2024-02-29 19:54 ` dpdklab
2024-02-29 19:55 ` |SUCCESS| " dpdklab
2024-02-29 19:55 ` |FAILURE| " dpdklab
2024-02-29 19:55 ` dpdklab
2024-02-29 19:55 ` |SUCCESS| " dpdklab
2024-02-29 19:56 ` |FAILURE| " dpdklab
2024-02-29 19:56 ` |SUCCESS| " dpdklab
2024-02-29 19:56 ` |FAILURE| " dpdklab
2024-02-29 19:56 ` |SUCCESS| " dpdklab
2024-02-29 19:57 ` |FAILURE| " dpdklab
2024-02-29 19:57 ` |SUCCESS| " dpdklab
2024-02-29 19:57 ` dpdklab
2024-02-29 19:57 ` dpdklab
2024-02-29 19:58 ` dpdklab
2024-02-29 19:58 ` dpdklab
2024-02-29 19:58 ` dpdklab
2024-02-29 19:58 ` dpdklab
2024-02-29 19:58 ` |FAILURE| " dpdklab
2024-02-29 19:59 ` dpdklab
2024-02-29 20:01 ` |SUCCESS| " dpdklab
2024-02-29 20:02 ` dpdklab
2024-02-29 20:02 ` dpdklab
2024-02-29 20:03 ` |FAILURE| " dpdklab
2024-02-29 20:04 ` dpdklab
2024-02-29 20:11 ` |SUCCESS| " dpdklab
2024-02-29 20:32 ` |FAILURE| " dpdklab
2024-02-29 20:46 ` |SUCCESS| " dpdklab
2024-02-29 20:48 ` dpdklab
2024-02-29 21:04 ` dpdklab
2024-03-01 2:57 ` dpdklab
2024-03-01 8:29 ` dpdklab
2024-03-01 8:34 ` dpdklab
2024-03-01 8:39 ` dpdklab
2024-03-01 8:44 ` dpdklab [this message]
2024-03-02 8:36 ` dpdklab
2024-03-03 9:36 ` dpdklab
2024-03-03 10:13 ` dpdklab
2024-03-03 10:42 ` 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=65e19552.170a0220.58b77.1c9dSMTPIN_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).