From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 5df34de5808a7b826b8bc035d6ee3161a12be364
Date: Sun, 03 Mar 2024 17:28:18 -0800 (PST) [thread overview]
Message-ID: <65e523b2.810a0220.711d5.1463SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
5df34de5808a7b826b8bc035d6ee3161a12be364 --> testing pass
Test environment and result as below:
+-----------------------+------------------------------+---------------------------+----------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+=======================+==============================+===========================+================+
| Debian 12 (arm) | PASS | PASS | PASS |
+-----------------------+------------------------------+---------------------------+----------------+
| Fedora 37 (ARM) | SKIPPED | SKIPPED | PASS |
+-----------------------+------------------------------+---------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+-----------------------+------------------------------+---------------------------+----------------+
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28289/
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-04 1:28 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 1:28 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-07 13:03 dpdklab
2024-03-07 12:14 dpdklab
2024-03-07 11:45 dpdklab
2024-03-04 2:41 dpdklab
2024-03-04 1:56 dpdklab
2024-03-04 1:44 dpdklab
2024-03-04 1:41 dpdklab
2024-03-04 1:39 dpdklab
2024-03-04 1:38 dpdklab
2024-03-04 1:36 dpdklab
2024-03-04 1:35 dpdklab
2024-03-04 1:35 dpdklab
2024-03-04 1:34 dpdklab
2024-03-04 1:33 dpdklab
2024-03-04 1:32 dpdklab
2024-03-04 1:30 dpdklab
2024-03-04 1:29 dpdklab
2024-03-04 1:29 dpdklab
2024-03-04 1:28 dpdklab
2024-03-04 1:28 dpdklab
2024-03-04 1:27 dpdklab
2024-03-04 1:27 dpdklab
2024-03-04 1:27 dpdklab
2024-03-04 1:26 dpdklab
2024-03-04 1:26 dpdklab
2024-03-04 1:25 dpdklab
2024-03-04 1:25 dpdklab
2024-03-04 1:25 dpdklab
2024-03-04 1:25 dpdklab
2024-03-04 1:25 dpdklab
2024-03-04 1:25 dpdklab
2024-03-04 1:25 dpdklab
2024-03-04 1:25 dpdklab
2024-03-04 1:24 dpdklab
2024-03-04 1:24 dpdklab
2024-03-04 1:24 dpdklab
2024-03-04 1:24 dpdklab
2024-03-04 1:23 dpdklab
2024-03-04 1:23 dpdklab
2024-03-04 1:23 dpdklab
2024-03-04 1:22 dpdklab
2024-03-04 1:22 dpdklab
2024-03-04 1:22 dpdklab
2024-03-04 1:22 dpdklab
2024-03-04 1:21 dpdklab
2024-03-04 1:20 dpdklab
2024-03-04 1:20 dpdklab
2024-03-04 1:19 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=65e523b2.810a0220.711d5.1463SMTPIN_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).