From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] cf4e3702412a8580bfe1fb8fff1db73517f7c796
Date: Sun, 22 Sep 2024 02:17:10 -0700 (PDT) [thread overview]
Message-ID: <66efe096.b00a0220.34de59.3a34SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk-next-net
cf4e3702412a8580bfe1fb8fff1db73517f7c796 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#304619
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| RHEL9 (ARM) | PEND |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PEND |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
| Debian 12 with MUSDK | PEND |
+------------------------------------+--------------------+
| Fedora 37 (ARM) | PEND |
+------------------------------------+--------------------+
| Fedora 38 (ARM) | PEND |
+------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PEND |
+------------------------------------+--------------------+
| Fedora 39 (ARM) | PEND |
+------------------------------------+--------------------+
| Fedora 39 (ARM Clang) | PEND |
+------------------------------------+--------------------+
| Fedora 40 (ARM) | PEND |
+------------------------------------+--------------------+
| Fedora 40 (ARM Clang) | PEND |
+------------------------------------+--------------------+
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
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
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)
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)
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
Fedora 40 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30703/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-09-22 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 9:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-22 6:56 dpdklab
2024-09-22 6: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=66efe096.b00a0220.34de59.3a34SMTPIN_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).