From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chenbo Xia <chenbox@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |SUCCESS| [GIT MASTER] fc10d6bd7632dff48a9f191e8d43872f47509e09
Date: Thu, 20 Jun 2024 08:10:34 -0700 (PDT) [thread overview]
Message-ID: <6674466a.050a0220.19e85.9236SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-virtio
fc10d6bd7632dff48a9f191e8d43872f47509e09 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| RHEL9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 40 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.1.1
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 22.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.0
Ubuntu 24.04 (ARM)
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29517/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-06-20 15:10 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 15:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-22 2:48 dpdklab
2024-06-20 22:41 dpdklab
2024-06-20 21:03 dpdklab
2024-06-20 18:09 dpdklab
2024-06-20 15:49 dpdklab
2024-06-20 15:48 dpdklab
2024-06-20 15:37 dpdklab
2024-06-20 15:29 dpdklab
2024-06-20 15:27 dpdklab
2024-06-20 15:23 dpdklab
2024-06-20 15:21 dpdklab
2024-06-20 15:19 dpdklab
2024-06-20 15:13 dpdklab
2024-06-20 15:11 dpdklab
2024-06-20 15:11 dpdklab
2024-06-20 15:10 dpdklab
2024-06-20 15:09 dpdklab
2024-06-20 15:09 dpdklab
2024-06-20 15:09 dpdklab
2024-06-20 15:09 dpdklab
2024-06-20 15:09 dpdklab
2024-06-20 15:08 dpdklab
2024-06-20 15:08 dpdklab
2024-06-20 15:05 dpdklab
2024-06-20 15:03 dpdklab
2024-06-20 15:03 dpdklab
2024-06-20 15:03 dpdklab
2024-06-20 15:02 dpdklab
2024-06-20 14:57 dpdklab
2024-06-20 14:55 dpdklab
2024-06-20 14:54 dpdklab
2024-06-20 14:53 dpdklab
2024-06-20 14:53 dpdklab
2024-06-20 14:52 dpdklab
2024-06-20 14:52 dpdklab
2024-06-20 14:51 dpdklab
2024-06-20 14:50 dpdklab
2024-06-20 14:50 dpdklab
2024-06-20 14:50 dpdklab
2024-06-20 14:49 dpdklab
2024-06-20 14:48 dpdklab
2024-06-20 14:48 dpdklab
2024-06-20 14:47 dpdklab
2024-06-20 14:46 dpdklab
2024-06-20 14:45 dpdklab
2024-06-20 14:44 dpdklab
2024-06-20 14:43 dpdklab
2024-06-20 14:42 dpdklab
2024-06-20 14:40 dpdklab
2024-06-20 14:38 dpdklab
2024-06-20 14:36 dpdklab
2024-06-20 14:35 dpdklab
2024-06-20 14:30 dpdklab
2024-06-20 14:30 dpdklab
2024-06-20 14:11 dpdklab
2024-06-20 14:08 dpdklab
2024-06-20 14:05 dpdklab
2024-06-20 14:05 dpdklab
2024-06-20 14:04 dpdklab
2024-06-20 13:47 dpdklab
2024-06-20 13:46 dpdklab
2024-06-20 13:44 dpdklab
2024-06-20 13:42 dpdklab
2024-06-20 13:42 dpdklab
2024-06-20 13:00 dpdklab
2024-06-20 12:59 dpdklab
2024-06-20 12:59 dpdklab
2024-06-20 12:58 dpdklab
2024-06-20 12:57 dpdklab
2024-06-20 12:55 dpdklab
2024-06-20 12:53 dpdklab
2024-06-20 10:21 dpdklab
2024-06-20 10:12 dpdklab
2024-06-20 10:03 dpdklab
2024-06-20 10:02 dpdklab
2024-06-20 10:01 dpdklab
2024-06-20 10:00 dpdklab
2024-06-20 9:59 dpdklab
2024-06-20 9:47 dpdklab
2024-06-20 9:46 dpdklab
2024-06-20 9:43 dpdklab
2024-06-20 9:40 dpdklab
2024-06-20 9:39 dpdklab
2024-06-20 9:38 dpdklab
2024-06-20 9:37 dpdklab
2024-06-20 9:34 dpdklab
2024-06-20 9:28 dpdklab
2024-06-20 9:26 dpdklab
2024-06-20 9:25 dpdklab
2024-06-20 9:18 dpdklab
2024-06-20 9:16 dpdklab
2024-06-20 9:15 dpdklab
2024-06-20 9:14 dpdklab
2024-06-20 9:12 dpdklab
2024-06-20 9:07 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=6674466a.050a0220.19e85.9236SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chenbox@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=maxime.coquelin@redhat.com \
--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).