From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] dde650220800850b58c81075cee3cf23c6fe593c
Date: Thu, 27 Jun 2024 04:56:56 -0700 (PDT) [thread overview]
Message-ID: <667d5388.050a0220.ecea3.24ddSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
dde650220800850b58c81075cee3cf23c6fe593c --> 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 |
+-----------------------------+------------------------------+---------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+-----------------------------+------------------------------+---------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+-----------------------------+------------------------------+---------------------------+----------------+
| 32-bit Ubuntu 20.04.4 (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
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
32-bit Ubuntu 20.04.4 (ARM)
Kernel: 5.4.0-155-generic aarch64
Compiler: gcc 9.4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29614/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-06-27 12:37 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 11:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-28 22:25 dpdklab
2024-06-28 5:00 dpdklab
2024-06-28 4:39 dpdklab
2024-06-27 13:41 dpdklab
2024-06-27 13:40 dpdklab
2024-06-27 13:33 dpdklab
2024-06-27 13:24 dpdklab
2024-06-27 13:19 dpdklab
2024-06-27 13:12 dpdklab
2024-06-27 12:49 dpdklab
2024-06-27 12:45 dpdklab
2024-06-27 12:43 dpdklab
2024-06-27 12:42 dpdklab
2024-06-27 12:41 dpdklab
2024-06-27 12:38 dpdklab
2024-06-27 12:38 dpdklab
2024-06-27 12:37 dpdklab
2024-06-27 12:34 dpdklab
2024-06-27 12:34 dpdklab
2024-06-27 12:32 dpdklab
2024-06-27 12:32 dpdklab
2024-06-27 12:31 dpdklab
2024-06-27 12:31 dpdklab
2024-06-27 12:30 dpdklab
2024-06-27 12:30 dpdklab
2024-06-27 12:28 dpdklab
2024-06-27 12:28 dpdklab
2024-06-27 12:26 dpdklab
2024-06-27 12:25 dpdklab
2024-06-27 12:25 dpdklab
2024-06-27 12:25 dpdklab
2024-06-27 12:24 dpdklab
2024-06-27 12:23 dpdklab
2024-06-27 12:23 dpdklab
2024-06-27 12:22 dpdklab
2024-06-27 12:21 dpdklab
2024-06-27 12:21 dpdklab
2024-06-27 12:21 dpdklab
2024-06-27 12:20 dpdklab
2024-06-27 12:19 dpdklab
2024-06-27 12:18 dpdklab
2024-06-27 12:17 dpdklab
2024-06-27 12:16 dpdklab
2024-06-27 12:15 dpdklab
2024-06-27 12:12 dpdklab
2024-06-27 12:12 dpdklab
2024-06-27 12:10 dpdklab
2024-06-27 12:05 dpdklab
2024-06-27 12:04 dpdklab
2024-06-27 12:02 dpdklab
2024-06-27 12:01 dpdklab
2024-06-27 11:58 dpdklab
2024-06-27 11:56 dpdklab
2024-06-27 11:54 dpdklab
2024-06-27 11:52 dpdklab
2024-06-27 11:43 dpdklab
2024-06-27 11:39 dpdklab
2024-06-27 11:36 dpdklab
2024-06-27 11:32 dpdklab
2024-06-27 11:29 dpdklab
2024-06-27 11:27 dpdklab
2024-06-27 11:22 dpdklab
2024-06-27 11:17 dpdklab
2024-06-27 11:14 dpdklab
2024-06-27 11:10 dpdklab
2024-06-27 11:10 dpdklab
2024-06-27 11:07 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=667d5388.050a0220.ecea3.24ddSMTPIN_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).