From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] e0dc4156c26bcb11c4348a079fa5fb8c4838423b
Date: Wed, 19 Jun 2024 18:13:45 -0700 (PDT) [thread overview]
Message-ID: <66738249.630a0220.2532a.7c48SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
e0dc4156c26bcb11c4348a079fa5fb8c4838423b --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| RHEL9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 40 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.1.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.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
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 22.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.0
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Ubuntu 24.04 (ARM)
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29507/
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 1:13 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 1:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-21 21:11 dpdklab
2024-06-20 8:35 dpdklab
2024-06-20 6:25 dpdklab
2024-06-20 3:43 dpdklab
2024-06-20 2:26 dpdklab
2024-06-20 2:26 dpdklab
2024-06-20 2:25 dpdklab
2024-06-20 2:24 dpdklab
2024-06-20 2:24 dpdklab
2024-06-20 2:23 dpdklab
2024-06-20 2:21 dpdklab
2024-06-20 1:50 dpdklab
2024-06-20 1:50 dpdklab
2024-06-20 1:49 dpdklab
2024-06-20 1:48 dpdklab
2024-06-20 1:47 dpdklab
2024-06-20 1:47 dpdklab
2024-06-20 1:47 dpdklab
2024-06-20 1:38 dpdklab
2024-06-20 1:33 dpdklab
2024-06-20 1:33 dpdklab
2024-06-20 1:33 dpdklab
2024-06-20 1:32 dpdklab
2024-06-20 1:32 dpdklab
2024-06-20 1:32 dpdklab
2024-06-20 1:31 dpdklab
2024-06-20 1:31 dpdklab
2024-06-20 1:31 dpdklab
2024-06-20 1:31 dpdklab
2024-06-20 1:31 dpdklab
2024-06-20 1:30 dpdklab
2024-06-20 1:29 dpdklab
2024-06-20 1:29 dpdklab
2024-06-20 1:29 dpdklab
2024-06-20 1:28 dpdklab
2024-06-20 1:28 dpdklab
2024-06-20 1:27 dpdklab
2024-06-20 1:26 dpdklab
2024-06-20 1:25 dpdklab
2024-06-20 1:25 dpdklab
2024-06-20 1:24 dpdklab
2024-06-20 1:23 dpdklab
2024-06-20 1:23 dpdklab
2024-06-20 1:22 dpdklab
2024-06-20 1:22 dpdklab
2024-06-20 1:20 dpdklab
2024-06-20 1:19 dpdklab
2024-06-20 1:19 dpdklab
2024-06-20 1:15 dpdklab
2024-06-20 1:14 dpdklab
2024-06-20 1:12 dpdklab
2024-06-20 1:06 dpdklab
2024-06-20 1:05 dpdklab
2024-06-20 1:05 dpdklab
2024-06-20 1:04 dpdklab
2024-06-20 0:58 dpdklab
2024-06-20 0:58 dpdklab
2024-06-20 0:57 dpdklab
2024-06-20 0:57 dpdklab
2024-06-20 0:57 dpdklab
2024-06-20 0:55 dpdklab
2024-06-20 0:54 dpdklab
2024-06-20 0:22 dpdklab
2024-06-20 0:21 dpdklab
2024-06-20 0:18 dpdklab
2024-06-20 0:10 dpdklab
2024-06-20 0:10 dpdklab
2024-06-20 0:09 dpdklab
2024-06-20 0:08 dpdklab
2024-06-20 0:04 dpdklab
2024-06-19 23:51 dpdklab
2024-06-19 23:48 dpdklab
2024-06-19 23:48 dpdklab
2024-06-19 21:04 dpdklab
2024-06-19 21:00 dpdklab
2024-06-19 20:53 dpdklab
2024-06-19 20:50 dpdklab
2024-06-19 20:49 dpdklab
2024-06-19 20:48 dpdklab
2024-06-19 20:47 dpdklab
2024-06-19 20:45 dpdklab
2024-06-19 20:44 dpdklab
2024-06-19 20:43 dpdklab
2024-06-19 20:40 dpdklab
2024-06-19 20:39 dpdklab
2024-06-19 20:38 dpdklab
2024-06-19 20:37 dpdklab
2024-06-19 20:37 dpdklab
2024-06-19 20:36 dpdklab
2024-06-19 20:36 dpdklab
2024-06-19 20:35 dpdklab
2024-06-19 20:34 dpdklab
2024-06-19 20:33 dpdklab
2024-06-19 20:05 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=66738249.630a0220.2532a.7c48SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=gakhil@marvell.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).