From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] dee3c01a2297538d7b65048aedfb372464f89942
Date: Wed, 21 Feb 2024 23:41:27 -0800 (PST) [thread overview]
Message-ID: <65d6faa7.050a0220.e2bc1.83d6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
dee3c01a2297538d7b65048aedfb372464f89942 --> testing pass
Test environment and result as below:
+-----------------------+---------------------------+------------------------------+--------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest | dpdk_unit_test |
+=======================+===========================+==============================+==============+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED | SKIPPED |
+-----------------------+---------------------------+------------------------------+--------------+----------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------+---------------------------+------------------------------+--------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | SKIPPED | PASS |
+-----------------------+---------------------------+------------------------------+--------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
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/28095/
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-22 7:41 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 7:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 22:22 dpdklab
2024-02-23 4:29 dpdklab
2024-02-23 4:22 dpdklab
2024-02-22 10:11 dpdklab
2024-02-22 9:05 dpdklab
2024-02-22 8:17 dpdklab
2024-02-22 7:58 dpdklab
2024-02-22 7:58 dpdklab
2024-02-22 7:56 dpdklab
2024-02-22 7:54 dpdklab
2024-02-22 7:54 dpdklab
2024-02-22 7:54 dpdklab
2024-02-22 7:50 dpdklab
2024-02-22 7:50 dpdklab
2024-02-22 7:50 dpdklab
2024-02-22 7:49 dpdklab
2024-02-22 7:49 dpdklab
2024-02-22 7:49 dpdklab
2024-02-22 7:49 dpdklab
2024-02-22 7:48 dpdklab
2024-02-22 7:46 dpdklab
2024-02-22 7:46 dpdklab
2024-02-22 7:45 dpdklab
2024-02-22 7:45 dpdklab
2024-02-22 7:44 dpdklab
2024-02-22 7:44 dpdklab
2024-02-22 7:44 dpdklab
2024-02-22 7:43 dpdklab
2024-02-22 7:42 dpdklab
2024-02-22 7:42 dpdklab
2024-02-22 7:41 dpdklab
2024-02-22 7:40 dpdklab
2024-02-22 7:40 dpdklab
2024-02-22 7:39 dpdklab
2024-02-22 7:39 dpdklab
2024-02-22 7:39 dpdklab
2024-02-22 7:39 dpdklab
2024-02-22 7:38 dpdklab
2024-02-22 7:38 dpdklab
2024-02-22 7:38 dpdklab
2024-02-22 7:38 dpdklab
2024-02-22 7:38 dpdklab
2024-02-22 7:37 dpdklab
2024-02-22 7:37 dpdklab
2024-02-22 7:37 dpdklab
2024-02-22 7:37 dpdklab
2024-02-22 7:36 dpdklab
2024-02-22 7:36 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=65d6faa7.050a0220.e2bc1.83d6SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).