From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] a89a9ca38ae61778a80f287677dc91e8bb3fbdfd
Date: Thu, 28 Sep 2023 19:15:37 -0700 (PDT) [thread overview]
Message-ID: <65163349.170a0220.72f8f.c8cdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
a89a9ca38ae61778a80f287677dc91e8bb3fbdfd --> 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/26296/
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-29 2:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 2:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 10:19 dpdklab
2023-09-29 2:52 dpdklab
2023-09-29 2:43 dpdklab
2023-09-29 2:40 dpdklab
2023-09-29 2:40 dpdklab
2023-09-29 2:31 dpdklab
2023-09-29 2:28 dpdklab
2023-09-29 2:24 dpdklab
2023-09-29 2:23 dpdklab
2023-09-29 2:17 dpdklab
2023-09-29 2:13 dpdklab
2023-09-29 2:09 dpdklab
2023-09-29 1:49 dpdklab
2023-09-29 1:45 dpdklab
2023-09-29 1:33 dpdklab
2023-09-29 1:32 dpdklab
2023-09-29 1:32 dpdklab
2023-09-29 1:32 dpdklab
2023-09-29 1:31 dpdklab
2023-09-29 1:30 dpdklab
2023-09-29 1:30 dpdklab
2023-09-29 1:30 dpdklab
2023-09-29 1:29 dpdklab
2023-09-29 1:29 dpdklab
2023-09-29 1:29 dpdklab
2023-09-29 1:29 dpdklab
2023-09-29 1:29 dpdklab
2023-09-29 1:29 dpdklab
2023-09-29 1:28 dpdklab
2023-09-29 1:28 dpdklab
2023-09-29 1:28 dpdklab
2023-09-29 1:28 dpdklab
2023-09-29 1:27 dpdklab
2023-09-29 1:27 dpdklab
2023-09-29 1:27 dpdklab
2023-09-29 1:27 dpdklab
2023-09-29 1:27 dpdklab
2023-09-29 1:26 dpdklab
2023-09-29 1:26 dpdklab
2023-09-29 1:26 dpdklab
2023-09-29 1:25 dpdklab
2023-09-29 1:25 dpdklab
2023-09-29 1:25 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=65163349.170a0220.72f8f.c8cdSMTPIN_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).