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] 0ba23e6339ab7230a64d83f12ddb5f2c46804e8a
Date: Mon, 13 Nov 2023 12:47:41 -0800 (PST) [thread overview]
Message-ID: <65528b6d.190a0220.7b377.57e3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
0ba23e6339ab7230a64d83f12ddb5f2c46804e8a --> testing pass
Test environment and result as below:
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| Environment | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+==========================+==============+===========================+==============================+================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED | SKIPPED | SKIPPED |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| Debian 11 (arm) | SKIPPED | PASS | PASS | SKIPPED |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | SKIPPED | PASS |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | SKIPPED | PASS |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
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/26975/
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-13 20:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 20:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-15 20:52 dpdklab
2023-11-15 20:29 dpdklab
2023-11-14 2:12 dpdklab
2023-11-13 23:09 dpdklab
2023-11-13 21:25 dpdklab
2023-11-13 21:11 dpdklab
2023-11-13 21:02 dpdklab
2023-11-13 20:56 dpdklab
2023-11-13 20:52 dpdklab
2023-11-13 20:48 dpdklab
2023-11-13 20:40 dpdklab
2023-11-13 20:40 dpdklab
2023-11-13 20:37 dpdklab
2023-11-13 20:35 dpdklab
2023-11-13 20:27 dpdklab
2023-11-13 20:26 dpdklab
2023-11-13 20:25 dpdklab
2023-11-13 20:22 dpdklab
2023-11-13 20:18 dpdklab
2023-11-13 20:18 dpdklab
2023-11-13 20:18 dpdklab
2023-11-13 20:17 dpdklab
2023-11-13 20:17 dpdklab
2023-11-13 20:17 dpdklab
2023-11-13 20:16 dpdklab
2023-11-13 20:16 dpdklab
2023-11-13 20:15 dpdklab
2023-11-13 20:14 dpdklab
2023-11-13 20:14 dpdklab
2023-11-13 20:14 dpdklab
2023-11-13 20:11 dpdklab
2023-11-13 20:05 dpdklab
2023-11-13 20:02 dpdklab
2023-11-13 19:57 dpdklab
2023-11-13 19:53 dpdklab
2023-11-13 19:43 dpdklab
2023-11-13 19:38 dpdklab
2023-11-13 19:14 dpdklab
2023-11-13 19:04 dpdklab
2023-11-13 19:02 dpdklab
2023-11-13 19:01 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=65528b6d.190a0220.7b377.57e3SMTPIN_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).