From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141230 [PATCH] [v3] ethdev: Add link_speed lanes support
Date: Tue, 18 Jun 2024 03:30:29 -0700 (PDT) [thread overview]
Message-ID: <667161c5.630a0220.3d50d.f029SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240617203448.97972-1-damodharam.ammepalli@broadcom.com>
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141230
_Testing PASS_
Submitter: Damodharam Ammepalli <damodharam.ammepalli@broadcom.com>
Date: Monday, June 17 2024 20:34:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fbba6db3640f9f623c29c452e1a6b057073e81d2
141230 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Debian Bullseye | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Fedora 39 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian 12 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| Fedora 40 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| RHEL9 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Ubuntu 24.04 | PASS |
+------------------+----------+
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Fedora 39
Kernel: Depends on container host
Compiler: clang 17.0.6
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 40
Kernel: Depends on container host
Compiler: clang 18.1.6
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30217/
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-06-18 10:30 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240617203448.97972-1-damodharam.ammepalli@broadcom.com>
2024-06-17 20:10 ` |SUCCESS| pw141230 [PATCH v3] " qemudev
2024-06-17 20:14 ` qemudev
2024-06-17 20:38 ` checkpatch
2024-06-17 21:24 ` |FAILURE| " 0-day Robot
2024-06-18 7:36 ` |SUCCESS| pw141230 [PATCH] [v3] " dpdklab
2024-06-18 7:40 ` dpdklab
2024-06-18 7:45 ` dpdklab
2024-06-18 7:49 ` dpdklab
2024-06-18 7:54 ` dpdklab
2024-06-18 8:56 ` dpdklab
2024-06-18 9:03 ` dpdklab
2024-06-18 9:04 ` dpdklab
2024-06-18 9:06 ` dpdklab
2024-06-18 9:06 ` dpdklab
2024-06-18 9:09 ` dpdklab
2024-06-18 9:10 ` dpdklab
2024-06-18 9:12 ` dpdklab
2024-06-18 9:14 ` dpdklab
2024-06-18 10:09 ` dpdklab
2024-06-18 10:11 ` dpdklab
2024-06-18 10:13 ` dpdklab
2024-06-18 10:13 ` dpdklab
2024-06-18 10:15 ` dpdklab
2024-06-18 10:15 ` dpdklab
2024-06-18 10:16 ` dpdklab
2024-06-18 10:17 ` dpdklab
2024-06-18 10:18 ` dpdklab
2024-06-18 10:19 ` dpdklab
2024-06-18 10:19 ` dpdklab
2024-06-18 10:21 ` dpdklab
2024-06-18 10:29 ` dpdklab
2024-06-18 10:30 ` dpdklab [this message]
2024-06-18 10:32 ` dpdklab
2024-06-18 10:35 ` dpdklab
2024-06-18 10:36 ` dpdklab
2024-06-18 10:52 ` dpdklab
2024-06-18 10:53 ` dpdklab
2024-06-18 10:53 ` dpdklab
2024-06-18 10:53 ` dpdklab
2024-06-18 10:55 ` dpdklab
2024-06-18 10:59 ` dpdklab
2024-06-18 11:00 ` dpdklab
2024-06-18 11:00 ` dpdklab
2024-06-18 11:01 ` dpdklab
2024-06-18 11:01 ` dpdklab
2024-06-18 11:01 ` dpdklab
2024-06-18 11:02 ` dpdklab
2024-06-18 11:03 ` dpdklab
2024-06-18 11:03 ` dpdklab
2024-06-18 11:05 ` dpdklab
2024-06-18 11:05 ` dpdklab
2024-06-18 11:05 ` dpdklab
2024-06-18 11:05 ` dpdklab
2024-06-18 11:06 ` dpdklab
2024-06-18 11:06 ` dpdklab
2024-06-18 11:07 ` dpdklab
2024-06-18 11:07 ` dpdklab
2024-06-18 11:08 ` dpdklab
2024-06-18 11:08 ` dpdklab
2024-06-18 11:08 ` dpdklab
2024-06-18 11:08 ` dpdklab
2024-06-18 11:09 ` dpdklab
2024-06-18 11:09 ` dpdklab
2024-06-18 11:09 ` dpdklab
2024-06-18 11:09 ` dpdklab
2024-06-18 11:10 ` dpdklab
2024-06-18 11:10 ` dpdklab
2024-06-18 11:10 ` dpdklab
2024-06-18 11:13 ` dpdklab
2024-06-18 11:14 ` dpdklab
2024-06-18 11:14 ` dpdklab
2024-06-18 11:15 ` dpdklab
2024-06-18 11:15 ` dpdklab
2024-06-18 11:15 ` dpdklab
2024-06-18 11:16 ` dpdklab
2024-06-18 11:16 ` dpdklab
2024-06-18 11:17 ` dpdklab
2024-06-18 11:22 ` dpdklab
2024-06-18 11:23 ` dpdklab
2024-06-18 11:23 ` dpdklab
2024-06-18 11:24 ` dpdklab
2024-06-18 11:25 ` dpdklab
2024-06-18 11:25 ` dpdklab
2024-06-18 11:26 ` dpdklab
2024-06-18 11:27 ` dpdklab
2024-06-18 11:27 ` dpdklab
2024-06-18 11:34 ` dpdklab
2024-06-18 11:55 ` dpdklab
2024-06-18 11:55 ` dpdklab
2024-06-18 11:58 ` dpdklab
2024-06-18 12:00 ` dpdklab
2024-06-18 12:01 ` dpdklab
2024-06-18 12:05 ` dpdklab
2024-06-18 12:17 ` dpdklab
2024-06-18 12:17 ` dpdklab
2024-06-18 12:17 ` dpdklab
2024-06-18 12:18 ` dpdklab
2024-06-18 12:25 ` dpdklab
2024-06-18 13:07 ` dpdklab
2024-06-18 13:08 ` dpdklab
2024-06-18 13:09 ` dpdklab
2024-06-18 13:20 ` dpdklab
2024-06-18 13:21 ` dpdklab
2024-06-18 13:21 ` dpdklab
2024-06-18 13:25 ` dpdklab
2024-06-18 13:27 ` dpdklab
2024-06-18 13:40 ` dpdklab
2024-06-18 13:43 ` dpdklab
2024-06-18 13:44 ` dpdklab
2024-06-18 14:03 ` dpdklab
2024-06-18 14:06 ` dpdklab
2024-06-18 14:49 ` dpdklab
2024-06-18 19:17 ` dpdklab
2024-06-18 19:32 ` dpdklab
2024-06-19 6:07 ` 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=667161c5.630a0220.3d50d.f029SMTPIN_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).