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] 3163106f00956156e206d7bc0e1dc258eee87535
Date: Wed, 21 Feb 2024 15:19:43 -0800 (PST) [thread overview]
Message-ID: <65d6850f.4a0a0220.ac2ed.77ebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
3163106f00956156e206d7bc0e1dc258eee87535 --> testing pass
Test environment and result as below:
+-----------------------+--------------+------------------------------+---------------------------+----------------+
| Environment | lpm_autotest | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_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 |
+-----------------------+--------------+------------------------------+---------------------------+----------------+
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28087/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-21 23:19 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 23:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 20:40 dpdklab
2024-02-23 4:59 dpdklab
2024-02-23 4:51 dpdklab
2024-02-22 0:33 dpdklab
2024-02-22 0:24 dpdklab
2024-02-22 0:21 dpdklab
2024-02-21 23:58 dpdklab
2024-02-21 23:53 dpdklab
2024-02-21 23:53 dpdklab
2024-02-21 23:29 dpdklab
2024-02-21 23:27 dpdklab
2024-02-21 23:21 dpdklab
2024-02-21 23:12 dpdklab
2024-02-21 23:05 dpdklab
2024-02-21 23:00 dpdklab
2024-02-21 22:53 dpdklab
2024-02-21 22:39 dpdklab
2024-02-21 22:32 dpdklab
2024-02-21 22:31 dpdklab
2024-02-21 22:26 dpdklab
2024-02-21 22:24 dpdklab
2024-02-21 22:23 dpdklab
2024-02-21 22:20 dpdklab
2024-02-21 22:19 dpdklab
2024-02-21 22:19 dpdklab
2024-02-21 22:17 dpdklab
2024-02-21 22:15 dpdklab
2024-02-21 22:14 dpdklab
2024-02-21 22:13 dpdklab
2024-02-21 22:12 dpdklab
2024-02-21 22:12 dpdklab
2024-02-21 22:11 dpdklab
2024-02-21 22:11 dpdklab
2024-02-21 22:11 dpdklab
2024-02-21 22:11 dpdklab
2024-02-21 22:10 dpdklab
2024-02-21 22:10 dpdklab
2024-02-21 22:09 dpdklab
2024-02-21 22:08 dpdklab
2024-02-21 22:08 dpdklab
2024-02-21 22:08 dpdklab
2024-02-21 22:08 dpdklab
2024-02-21 22:08 dpdklab
2024-02-21 22:02 dpdklab
2024-02-21 22:02 dpdklab
2024-02-21 22:01 dpdklab
2024-02-21 22:00 dpdklab
2024-02-21 21:58 dpdklab
2024-02-21 21:55 dpdklab
2024-02-21 21:44 dpdklab
2024-02-21 21:42 dpdklab
2024-02-21 21:41 dpdklab
2024-02-21 21:36 dpdklab
2024-02-21 21:35 dpdklab
2024-02-21 21:34 dpdklab
2024-02-21 21:33 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=65d6850f.4a0a0220.ac2ed.77ebSMTPIN_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).