From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] f4ccce58c1a33cb41e1e820da504698437987efc
Date: Thu, 21 Nov 2024 11:39:50 -0800 (PST) [thread overview]
Message-ID: <673f8c86.050a0220.2a55e3.079dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk-next-crypto
f4ccce58c1a33cb41e1e820da504698437987efc --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#336573
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| RHEL9 (ARM) | PEND |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PEND |
+------------------------------------+--------------------+
| Debian 12 with MUSDK | PEND |
+------------------------------------+--------------------+
| Ubuntu 22.04 (ARM) | PEND |
+------------------------------------+--------------------+
| Debian 12 (arm) | PEND |
+------------------------------------+--------------------+
| Fedora 39 (ARM) | PEND |
+------------------------------------+--------------------+
| Fedora 39 (ARM Clang) | PEND |
+------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PEND |
+------------------------------------+--------------------+
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: Depends on container host
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Debian 12 with MUSDK
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Ubuntu 22.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
Fedora 39 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
CentOS Stream 9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31672/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-11-21 19:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 19:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-21 20:02 dpdklab
2024-11-21 19:59 dpdklab
2024-11-21 19:39 dpdklab
2024-11-21 19:36 dpdklab
2024-11-21 19:27 dpdklab
2024-11-21 19:06 dpdklab
2024-11-21 18:34 dpdklab
2024-11-21 18:29 dpdklab
2024-11-21 17:50 dpdklab
2024-11-21 17:50 dpdklab
2024-11-21 17:40 dpdklab
2024-11-21 17:30 dpdklab
2024-11-21 12:08 dpdklab
2024-11-21 12:04 dpdklab
2024-11-21 11:58 dpdklab
2024-11-21 11:57 dpdklab
2024-11-21 8:06 dpdklab
2024-11-21 7:56 dpdklab
2024-11-21 7:53 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=673f8c86.050a0220.2a55e3.079dSMTPIN_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).