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] a335e300cac3adb53fe0aa81d46d4e3450f69b66
Date: Tue, 14 Nov 2023 09:02:29 -0800 (PST) [thread overview]
Message-ID: <6553a825.170a0220.45774.accaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
a335e300cac3adb53fe0aa81d46d4e3450f69b66 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26992/
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-14 17:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 17:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-16 9:32 dpdklab
2023-11-16 9:22 dpdklab
2023-11-14 20:51 dpdklab
2023-11-14 20:43 dpdklab
2023-11-14 20:26 dpdklab
2023-11-14 19:36 dpdklab
2023-11-14 18:17 dpdklab
2023-11-14 18:04 dpdklab
2023-11-14 17:56 dpdklab
2023-11-14 17:49 dpdklab
2023-11-14 17:31 dpdklab
2023-11-14 17:30 dpdklab
2023-11-14 17:29 dpdklab
2023-11-14 17:25 dpdklab
2023-11-14 17:25 dpdklab
2023-11-14 17:22 dpdklab
2023-11-14 17:20 dpdklab
2023-11-14 17:18 dpdklab
2023-11-14 17:17 dpdklab
2023-11-14 17:16 dpdklab
2023-11-14 17:16 dpdklab
2023-11-14 17:16 dpdklab
2023-11-14 17:16 dpdklab
2023-11-14 17:16 dpdklab
2023-11-14 17:16 dpdklab
2023-11-14 17:14 dpdklab
2023-11-14 17:13 dpdklab
2023-11-14 17:13 dpdklab
2023-11-14 17:13 dpdklab
2023-11-14 17:11 dpdklab
2023-11-14 17:11 dpdklab
2023-11-14 17:09 dpdklab
2023-11-14 17:09 dpdklab
2023-11-14 17:06 dpdklab
2023-11-14 17:04 dpdklab
2023-11-14 17:02 dpdklab
2023-11-14 17:02 dpdklab
2023-11-14 16:58 dpdklab
2023-11-14 16:58 dpdklab
2023-11-14 16:56 dpdklab
2023-11-14 16:55 dpdklab
2023-11-14 16:54 dpdklab
2023-11-14 16:52 dpdklab
2023-11-14 16:51 dpdklab
2023-11-14 16:49 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=6553a825.170a0220.45774.accaSMTPIN_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).