From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] c4b6f6ff54c32e922971e1403f19aba9ea614896
Date: Sun, 27 Apr 2025 21:25:27 -0700 (PDT) [thread overview]
Message-ID: <680f0337.050a0220.1bdfbf.4152SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v23.11
c4b6f6ff54c32e922971e1403f19aba9ea614896 --> testing pending
Upstream job id: Generic-DPDK-Compile-ABI#124611
Test environment and result as below:
+-------------------+----------+
| Environment | abi_test |
+===================+==========+
| CentOS Stream 9 | PASS |
+-------------------+----------+
| CentOS Stream 10 | PEND |
+-------------------+----------+
| Debian 12 | PEND |
+-------------------+----------+
| Fedora 40 (Clang) | PEND |
+-------------------+----------+
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
CentOS Stream 10
Kernel: Depends on container host
Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/33373/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-04-28 4:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 4:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-28 5:15 dpdklab
2025-04-28 4:46 dpdklab
2025-04-27 7:20 dpdklab
2025-04-27 7:18 dpdklab
2025-04-27 6:43 dpdklab
2025-04-26 5:57 dpdklab
2025-04-26 5:45 dpdklab
2025-04-26 4:54 dpdklab
2025-04-24 6:27 dpdklab
2025-04-24 5:41 dpdklab
2025-04-24 5:23 dpdklab
2025-04-24 5:01 dpdklab
2025-04-23 7:38 dpdklab
2025-04-23 6:28 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=680f0337.050a0220.1bdfbf.4152SMTPIN_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).