From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] f197f1e13ccfb74c92ad05602443dd0984f39540
Date: Tue, 10 Dec 2024 23:27:44 -0800 (PST) [thread overview]
Message-ID: <67593eef.050a0220.3a84a7.02d6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: tags/v21.11
f197f1e13ccfb74c92ad05602443dd0984f39540 --> testing pass
Upstream job id: Generic-DPDK-Compile-Meson#342660
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+------------------------------------+--------------------+
| RHEL9 (ARM) | PASS |
+------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+------------------------------------+--------------------+
| Fedora 40 (ARM Clang) | PASS |
+------------------------------------+--------------------+
| Fedora 39 (ARM Clang) | PASS |
+------------------------------------+--------------------+
| Ubuntu 24.04 (ARM) | PASS |
+------------------------------------+--------------------+
| Ubuntu 22.04 (ARM) | PASS |
+------------------------------------+--------------------+
| Fedora 40 (ARM) | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+------------------------------------+--------------------+
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
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian 12 with MUSDK
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
Fedora 40 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
Fedora 39 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
Ubuntu 24.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Ubuntu 22.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
Ubuntu 20.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
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/31895/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-11 7:27 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 7:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 8:05 dpdklab
2024-12-11 7:36 dpdklab
2024-12-11 7:19 dpdklab
2024-12-11 7:09 dpdklab
2024-12-11 6:46 dpdklab
2024-12-11 6:36 dpdklab
2024-12-11 6:33 dpdklab
2024-12-11 6:28 dpdklab
2024-12-11 5:54 dpdklab
2024-12-11 5:53 dpdklab
2024-12-11 5:53 dpdklab
2024-12-10 8:27 dpdklab
2024-12-10 7:40 dpdklab
2024-12-10 7:22 dpdklab
2024-12-10 7:22 dpdklab
2024-12-10 7:20 dpdklab
2024-12-10 6:42 dpdklab
2024-12-10 6:42 dpdklab
2024-12-10 6:28 dpdklab
2024-12-10 6:00 dpdklab
2024-12-10 6:00 dpdklab
2024-12-10 5:40 dpdklab
2024-12-09 7:35 dpdklab
2024-12-09 7:29 dpdklab
2024-12-09 7:26 dpdklab
2024-12-09 6:45 dpdklab
2024-12-09 6:06 dpdklab
2024-12-09 6:03 dpdklab
2024-12-09 5:33 dpdklab
2024-12-09 5:30 dpdklab
2024-12-09 5:27 dpdklab
2024-12-08 7:16 dpdklab
2024-12-08 7:06 dpdklab
2024-12-08 6:41 dpdklab
2024-12-08 6:39 dpdklab
2024-12-08 6:38 dpdklab
2024-12-08 6:36 dpdklab
2024-12-08 6:23 dpdklab
2024-12-08 6:00 dpdklab
2024-12-08 5:48 dpdklab
2024-12-08 5:47 dpdklab
2024-12-08 5:39 dpdklab
2024-12-07 8:25 dpdklab
2024-12-07 8:23 dpdklab
2024-12-07 8:13 dpdklab
2024-12-07 8:10 dpdklab
2024-12-07 8:03 dpdklab
2024-12-07 7:58 dpdklab
2024-12-07 7:50 dpdklab
2024-12-07 7:48 dpdklab
2024-12-07 7:44 dpdklab
2024-12-07 7:38 dpdklab
2024-12-07 7:14 dpdklab
2024-12-07 6:59 dpdklab
2024-12-07 6:46 dpdklab
2024-12-07 6:36 dpdklab
2024-12-07 6:29 dpdklab
2024-12-07 6:08 dpdklab
2024-12-07 5:42 dpdklab
2024-12-07 3:23 dpdklab
2024-12-07 3:18 dpdklab
2024-12-07 1:47 dpdklab
2024-12-07 1:46 dpdklab
2024-12-07 1:46 dpdklab
2024-12-07 1:45 dpdklab
2024-12-06 7:27 dpdklab
2024-12-06 6:55 dpdklab
2024-12-06 5:54 dpdklab
2024-12-06 5:51 dpdklab
2024-12-06 5:33 dpdklab
2024-12-06 5:28 dpdklab
2024-12-06 5:23 dpdklab
2024-12-05 10:19 dpdklab
2024-12-05 9:29 dpdklab
2024-12-05 9:18 dpdklab
2024-12-05 8:52 dpdklab
2024-12-05 8:01 dpdklab
2024-12-05 7:42 dpdklab
2024-12-05 7:31 dpdklab
2024-12-05 7:26 dpdklab
2024-12-05 7:18 dpdklab
2024-12-05 7:08 dpdklab
2024-12-05 6:29 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=67593eef.050a0220.3a84a7.02d6SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--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).