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, Xueming Li <xuemingl@nvidia.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 04536b2361c4e3373f0cdc429a6637fe1afdbdb4
Date: Sun, 21 Dec 2025 23:36:47 -0800 (PST)	[thread overview]
Message-ID: <6948f50f.050a0220.1a4182.7587SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: tags/v22.11

04536b2361c4e3373f0cdc429a6637fe1afdbdb4 --> testing pass

Upstream job id: Generic-DPDK-Compile-ABI#136135

Test environment and result as below:

+------------------------------+----------+
|         Environment          | abi_test |
+==============================+==========+
| Debian GNU/Linux 12          | PASS     |
+------------------------------+----------+
| CentOS Stream 9              | PASS     |
+------------------------------+----------+
| Ubuntu 24.04                 | PASS     |
+------------------------------+----------+
| CentOS Stream 10             | PASS     |
+------------------------------+----------+
| Red Hat Enterprise Linux 9.7 | PASS     |
+------------------------------+----------+
| Fedora Linux 42              | PASS     |
+------------------------------+----------+
| openSUSE Leap 15.6           | PASS     |
+------------------------------+----------+
| Ubuntu 22.04                 | PASS     |
+------------------------------+----------+


Debian GNU/Linux 12
	Kernel: 5.15
	Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0

CentOS Stream 9
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-14)

Ubuntu 24.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

CentOS Stream 10
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 14.3.1 20251022 (Red Hat 14.3.1-4)

Red Hat Enterprise Linux 9.7
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)

Fedora Linux 42
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)

openSUSE Leap 15.6
	Kernel: 5.15
	Compiler: gcc gcc (SUSE Linux) 7.5.0

Ubuntu 22.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/35908/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2025-12-22  7:36 UTC|newest]

Thread overview: 129+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22  7:36 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-22 11:15 dpdklab
2025-12-22  9:52 dpdklab
2025-12-22  8:20 dpdklab
2025-12-22  7:51 dpdklab
2025-12-22  7:36 dpdklab
2025-12-22  6:57 dpdklab
2025-12-22  6:35 dpdklab
2025-12-22  6:28 dpdklab
2025-12-22  6:27 dpdklab
2025-12-22  6:27 dpdklab
2025-12-22  5:41 dpdklab
2025-12-22  5:32 dpdklab
2025-12-22  5:29 dpdklab
2025-12-21  8:58 dpdklab
2025-12-21  7:32 dpdklab
2025-12-21  7:20 dpdklab
2025-12-21  6:29 dpdklab
2025-12-21  6:29 dpdklab
2025-12-21  6:27 dpdklab
2025-12-21  5:32 dpdklab
2025-12-21  5:29 dpdklab
2025-12-21  1:30 dpdklab
2025-12-20  7:39 dpdklab
2025-12-20  7:39 dpdklab
2025-12-20  7:38 dpdklab
2025-12-20  7:37 dpdklab
2025-12-20  6:29 dpdklab
2025-12-20  6:26 dpdklab
2025-12-20  6:26 dpdklab
2025-12-20  5:42 dpdklab
2025-12-20  5:29 dpdklab
2025-12-20  5:17 dpdklab
2025-12-20  1:50 dpdklab
2025-12-19  9:37 dpdklab
2025-12-19  8:50 dpdklab
2025-12-19  8:49 dpdklab
2025-12-19  8:12 dpdklab
2025-12-19  7:42 dpdklab
2025-12-19  7:24 dpdklab
2025-12-19  7:14 dpdklab
2025-12-19  7:12 dpdklab
2025-12-19  6:26 dpdklab
2025-12-19  6:26 dpdklab
2025-12-19  6:20 dpdklab
2025-12-19  5:42 dpdklab
2025-12-19  5:41 dpdklab
2025-12-19  1:23 dpdklab
2025-12-18 18:50 dpdklab
2025-12-18  9:11 dpdklab
2025-12-18  9:11 dpdklab
2025-12-18  8:19 dpdklab
2025-12-18  6:26 dpdklab
2025-12-18  6:26 dpdklab
2025-12-18  6:26 dpdklab
2025-12-18  5:47 dpdklab
2025-12-18  5:31 dpdklab
2025-12-18  5:29 dpdklab
2025-12-18  5:28 dpdklab
2025-12-18  0:23 dpdklab
2025-12-18  0:23 dpdklab
2025-12-17 21:00 dpdklab
2025-12-17 19:01 dpdklab
2025-12-17 19:00 dpdklab
2025-12-17 19:00 dpdklab
2025-12-17 19:00 dpdklab
2025-12-17 19:00 dpdklab
2025-12-17 19:00 dpdklab
2025-12-17 16:21 dpdklab
2025-12-17 16:16 dpdklab
2025-12-17 16:13 dpdklab
2025-12-17 15:58 dpdklab
2025-12-17 15:58 dpdklab
2025-12-17 15:57 dpdklab
2025-12-17 15:57 dpdklab
2025-12-17 15:54 dpdklab
2025-12-16  9:29 dpdklab
2025-12-16  9:21 dpdklab
2025-12-16  8:36 dpdklab
2025-12-16  8:24 dpdklab
2025-12-16  7:55 dpdklab
2025-12-16  7:55 dpdklab
2025-12-16  7:55 dpdklab
2025-12-16  7:55 dpdklab
2025-12-16  7:27 dpdklab
2025-12-16  6:49 dpdklab
2025-12-16  6:27 dpdklab
2025-12-16  6:21 dpdklab
2025-12-16  5:55 dpdklab
2025-12-16  5:47 dpdklab
2025-12-16  5:33 dpdklab
2025-12-16  5:21 dpdklab
2025-12-15 10:00 dpdklab
2025-12-15  8:22 dpdklab
2025-12-15  8:07 dpdklab
2025-12-15  7:58 dpdklab
2025-12-15  7:14 dpdklab
2025-12-15  7:14 dpdklab
2025-12-15  6:25 dpdklab
2025-12-15  6:02 dpdklab
2025-12-15  5:45 dpdklab
2025-12-15  5:29 dpdklab
2025-12-15  5:17 dpdklab
2025-12-15  5:16 dpdklab
2025-12-14  9:14 dpdklab
2025-12-14  7:31 dpdklab
2025-12-14  7:31 dpdklab
2025-12-14  7:31 dpdklab
2025-12-14  7:30 dpdklab
2025-12-14  7:30 dpdklab
2025-12-14  7:29 dpdklab
2025-12-14  7:11 dpdklab
2025-12-14  6:27 dpdklab
2025-12-14  6:26 dpdklab
2025-12-14  5:30 dpdklab
2025-12-14  5:17 dpdklab
2025-12-13 10:06 dpdklab
2025-12-13  8:50 dpdklab
2025-12-13  8:11 dpdklab
2025-12-13  7:41 dpdklab
2025-12-13  7:38 dpdklab
2025-12-13  7:37 dpdklab
2025-12-13  7:36 dpdklab
2025-12-13  7:23 dpdklab
2025-12-13  7:17 dpdklab
2025-12-13  7:12 dpdklab
2025-12-13  6:26 dpdklab
2025-12-13  6:20 dpdklab
2025-12-13  5:33 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=6948f50f.050a0220.1a4182.7587SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).