From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] c56185fc183fc0532d2f03aaf04bbf0989ea91a5
Date: Wed, 27 Sep 2023 18:15:57 -0700 (PDT) [thread overview]
Message-ID: <6514d3cd.170a0220.d4ca3.5d25SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
c56185fc183fc0532d2f03aaf04bbf0989ea91a5 --> testing pass
Test environment and result as below:
+----------------------+---------------------------+------------------------------+--------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest |
+======================+===========================+==============================+==============+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+----------------------+---------------------------+------------------------------+--------------+
| Ubuntu 20.04 ARM SVE | 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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26271/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-28 1:16 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 1:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-28 2:18 dpdklab
2023-09-28 1:43 dpdklab
2023-09-28 1:42 dpdklab
2023-09-28 1:38 dpdklab
2023-09-28 1:35 dpdklab
2023-09-28 1:31 dpdklab
2023-09-28 1:31 dpdklab
2023-09-28 1:30 dpdklab
2023-09-28 1:25 dpdklab
2023-09-28 1:23 dpdklab
2023-09-28 1:21 dpdklab
2023-09-28 1:17 dpdklab
2023-09-28 1:17 dpdklab
2023-09-28 1:16 dpdklab
2023-09-28 1:12 dpdklab
2023-09-28 1:09 dpdklab
2023-09-28 1:09 dpdklab
2023-09-28 1:09 dpdklab
2023-09-28 1:08 dpdklab
2023-09-28 1:08 dpdklab
2023-09-28 1:08 dpdklab
2023-09-28 1:07 dpdklab
2023-09-28 1:07 dpdklab
2023-09-28 1:06 dpdklab
2023-09-28 1:06 dpdklab
2023-09-28 1:06 dpdklab
2023-09-28 1:05 dpdklab
2023-09-28 1:05 dpdklab
2023-09-28 1:05 dpdklab
2023-09-28 1:05 dpdklab
2023-09-28 1:05 dpdklab
2023-09-28 1:05 dpdklab
2023-09-28 1:05 dpdklab
2023-09-28 1:04 dpdklab
2023-09-28 1:03 dpdklab
2023-09-28 1:02 dpdklab
2023-09-28 1:02 dpdklab
2023-09-28 1:02 dpdklab
2023-09-28 1:02 dpdklab
2023-09-28 1:01 dpdklab
2023-09-28 1:00 dpdklab
2023-09-28 0:59 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=6514d3cd.170a0220.d4ca3.5d25SMTPIN_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).