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] 11e5ca63c77b355d0397f642989f28a7a0318cbc
Date: Fri, 03 Nov 2023 10:06:57 -0700 (PDT) [thread overview]
Message-ID: <654528b1.170a0220.bf20.6138SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
11e5ca63c77b355d0397f642989f28a7a0318cbc --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26813/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-03 17:06 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 17:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-03 19:43 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 17:58 dpdklab
2023-11-03 17:50 dpdklab
2023-11-03 17:45 dpdklab
2023-11-03 17:19 dpdklab
2023-11-03 17:17 dpdklab
2023-11-03 17:16 dpdklab
2023-11-03 17:10 dpdklab
2023-11-03 17:09 dpdklab
2023-11-03 17:08 dpdklab
2023-11-03 17:07 dpdklab
2023-11-03 17:06 dpdklab
2023-11-03 17:05 dpdklab
2023-11-03 17:04 dpdklab
2023-11-03 17:04 dpdklab
2023-11-03 17:03 dpdklab
2023-11-03 16:56 dpdklab
2023-11-03 16:55 dpdklab
2023-11-03 16:55 dpdklab
2023-11-03 16:54 dpdklab
2023-11-03 16:53 dpdklab
2023-11-03 16:49 dpdklab
2023-11-03 16:49 dpdklab
2023-11-03 16:48 dpdklab
2023-11-03 16:44 dpdklab
2023-11-03 16:43 dpdklab
2023-11-03 16:43 dpdklab
2023-11-03 16:42 dpdklab
2023-11-03 16:42 dpdklab
2023-11-03 16:41 dpdklab
2023-11-03 16:41 dpdklab
2023-11-03 16:41 dpdklab
2023-11-03 16:41 dpdklab
2023-11-03 16:41 dpdklab
2023-11-03 16:40 dpdklab
2023-11-03 16:40 dpdklab
2023-11-03 16:40 dpdklab
2023-11-03 16:39 dpdklab
2023-11-03 16:39 dpdklab
2023-11-03 16:39 dpdklab
2023-11-03 16:38 dpdklab
2023-11-03 16:38 dpdklab
2023-11-03 16:38 dpdklab
2023-11-03 16:37 dpdklab
2023-11-03 16:37 dpdklab
2023-11-03 16:36 dpdklab
2023-11-03 16:36 dpdklab
2023-11-03 16:35 dpdklab
2023-11-03 16:34 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=654528b1.170a0220.bf20.6138SMTPIN_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).