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] 2a26b270c049f635c76673f94d21b2901c89c2e8
Date: Fri, 10 Nov 2023 09:16:43 -0800 (PST) [thread overview]
Message-ID: <654e657b.810a0220.ec5ba.40afSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
2a26b270c049f635c76673f94d21b2901c89c2e8 --> testing pass
Test environment and result as below:
+--------------------------+---------------------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+==========================+===========================+================+
| Debian 11 (arm) | PASS | SKIPPED |
+--------------------------+---------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | PASS |
+--------------------------+---------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | PASS |
+--------------------------+---------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.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/26940/
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-10 17:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 17:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-14 19:53 dpdklab
2023-11-14 19:42 dpdklab
2023-11-10 23:39 dpdklab
2023-11-10 18:40 dpdklab
2023-11-10 18:37 dpdklab
2023-11-10 17:33 dpdklab
2023-11-10 17:32 dpdklab
2023-11-10 17:31 dpdklab
2023-11-10 17:29 dpdklab
2023-11-10 17:27 dpdklab
2023-11-10 17:26 dpdklab
2023-11-10 17:23 dpdklab
2023-11-10 17:23 dpdklab
2023-11-10 17:23 dpdklab
2023-11-10 17:23 dpdklab
2023-11-10 17:22 dpdklab
2023-11-10 17:22 dpdklab
2023-11-10 17:22 dpdklab
2023-11-10 17:21 dpdklab
2023-11-10 17:21 dpdklab
2023-11-10 17:20 dpdklab
2023-11-10 17:19 dpdklab
2023-11-10 17:19 dpdklab
2023-11-10 17:18 dpdklab
2023-11-10 17:16 dpdklab
2023-11-10 17:16 dpdklab
2023-11-10 17:15 dpdklab
2023-11-10 17:15 dpdklab
2023-11-10 17:14 dpdklab
2023-11-10 17:14 dpdklab
2023-11-10 17:14 dpdklab
2023-11-10 17:14 dpdklab
2023-11-10 17:14 dpdklab
2023-11-10 17:13 dpdklab
2023-11-10 17:12 dpdklab
2023-11-10 17:12 dpdklab
2023-11-10 17:12 dpdklab
2023-11-10 17:10 dpdklab
2023-11-10 17:10 dpdklab
2023-11-10 17:08 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=654e657b.810a0220.ec5ba.40afSMTPIN_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).