From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 38543d33bd47fc0ee21f59db80a8763620741879
Date: Tue, 05 Aug 2025 17:28:56 -0700 (PDT) [thread overview]
Message-ID: <6892a1c8.170a0220.31c7c6.46f9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk
38543d33bd47fc0ee21f59db80a8763620741879 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#415094
Test environment and result as below:
+------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PEND |
+------------------------------+--------------------+
| Ubuntu 20.04 | PEND |
+------------------------------+--------------------+
| Fedora Linux 40 | PEND |
+------------------------------+--------------------+
| Fedora Linux 41 | PEND |
+------------------------------+--------------------+
Red Hat Enterprise Linux 9.5
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04
Kernel: 5.15
Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Fedora Linux 40
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 41
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/34497/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-08-06 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 0:28 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-04 0:29 dpdklab
2025-08-02 0:36 dpdklab
2025-08-01 0:16 dpdklab
2025-07-30 0:34 dpdklab
2025-07-30 0:19 dpdklab
2025-07-30 0:17 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=6892a1c8.170a0220.31c7c6.46f9SMTPIN_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).