From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] c29202f2f70abd22e3d74e0671ec9f6cb9e387ee
Date: Wed, 27 Mar 2024 17:35:45 -0700 (PDT) [thread overview]
Message-ID: <6604bb61.050a0220.10a07.137dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
c29202f2f70abd22e3d74e0671ec9f6cb9e387ee --> testing pass
Test environment and result as below:
+-----------------------+---------------------------+------------------------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+=======================+===========================+==============================+================+
| Debian 12 (arm) | PASS | PASS | PASS |
+-----------------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+-----------------------+---------------------------+------------------------------+----------------+
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28653/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-28 0:37 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 0:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-02 13:06 dpdklab
2024-04-02 13:02 dpdklab
2024-04-02 12:58 dpdklab
2024-04-02 12:54 dpdklab
2024-04-02 12:47 dpdklab
2024-03-28 3:08 dpdklab
2024-03-28 1:43 dpdklab
2024-03-28 1:41 dpdklab
2024-03-28 1:33 dpdklab
2024-03-28 1:05 dpdklab
2024-03-28 0:59 dpdklab
2024-03-28 0:59 dpdklab
2024-03-28 0:57 dpdklab
2024-03-28 0:54 dpdklab
2024-03-28 0:53 dpdklab
2024-03-28 0:53 dpdklab
2024-03-28 0:51 dpdklab
2024-03-28 0:51 dpdklab
2024-03-28 0:49 dpdklab
2024-03-28 0:48 dpdklab
2024-03-28 0:48 dpdklab
2024-03-28 0:48 dpdklab
2024-03-28 0:45 dpdklab
2024-03-28 0:44 dpdklab
2024-03-28 0:44 dpdklab
2024-03-28 0:43 dpdklab
2024-03-28 0:42 dpdklab
2024-03-28 0:42 dpdklab
2024-03-28 0:42 dpdklab
2024-03-28 0:40 dpdklab
2024-03-28 0:39 dpdklab
2024-03-28 0:39 dpdklab
2024-03-28 0:38 dpdklab
2024-03-28 0:38 dpdklab
2024-03-28 0:38 dpdklab
2024-03-28 0:38 dpdklab
2024-03-28 0:38 dpdklab
2024-03-28 0:37 dpdklab
2024-03-28 0:37 dpdklab
2024-03-28 0:37 dpdklab
2024-03-28 0:37 dpdklab
2024-03-28 0:37 dpdklab
2024-03-28 0:36 dpdklab
2024-03-28 0:36 dpdklab
2024-03-28 0:36 dpdklab
2024-03-28 0:36 dpdklab
2024-03-28 0:36 dpdklab
2024-03-28 0:36 dpdklab
2024-03-28 0:36 dpdklab
2024-03-28 0:36 dpdklab
2024-03-28 0:35 dpdklab
2024-03-28 0:35 dpdklab
2024-03-28 0:35 dpdklab
2024-03-28 0:35 dpdklab
2024-03-28 0:35 dpdklab
2024-03-28 0:35 dpdklab
2024-03-28 0:34 dpdklab
2024-03-28 0:34 dpdklab
2024-03-28 0:34 dpdklab
2024-03-28 0:34 dpdklab
2024-03-28 0:34 dpdklab
2024-03-28 0:34 dpdklab
2024-03-28 0:33 dpdklab
2024-03-28 0:33 dpdklab
2024-03-28 0:33 dpdklab
2024-03-28 0:32 dpdklab
2024-03-28 0:32 dpdklab
2024-03-28 0:32 dpdklab
2024-03-28 0:32 dpdklab
2024-03-28 0:32 dpdklab
2024-03-28 0:31 dpdklab
2024-03-28 0:31 dpdklab
2024-03-28 0:31 dpdklab
2024-03-28 0:31 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=6604bb61.050a0220.10a07.137dSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).