From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135136-135172 [PATCH] [v3,37/37] crypto/dpaa_sec, crypto
Date: Wed, 13 Dec 2023 12:01:21 -0800 (PST) [thread overview]
Message-ID: <657a0d91.050a0220.7a9e.ba78SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135172
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, December 13 2023 16:36:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
135136-135172 --> testing pass
Test environment and result as below:
+--------------------------+---------------------------+------------------------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+==========================+===========================+==============================+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+--------------------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.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/patchsets/28611/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-13 20:01 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 20:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-13 23:45 dpdklab
2023-12-13 23:39 dpdklab
2023-12-13 23:35 dpdklab
2023-12-13 23:17 dpdklab
2023-12-13 22:02 dpdklab
2023-12-13 21:53 dpdklab
2023-12-13 21:48 dpdklab
2023-12-13 21:46 dpdklab
2023-12-13 21:38 dpdklab
2023-12-13 21:33 dpdklab
2023-12-13 21:28 dpdklab
2023-12-13 21:26 dpdklab
2023-12-13 21:24 dpdklab
2023-12-13 21:23 dpdklab
2023-12-13 21:22 dpdklab
2023-12-13 21:21 dpdklab
2023-12-13 21:19 dpdklab
2023-12-13 21:14 dpdklab
2023-12-13 21:14 dpdklab
2023-12-13 21:10 dpdklab
2023-12-13 21:08 dpdklab
2023-12-13 21:07 dpdklab
2023-12-13 21:05 dpdklab
2023-12-13 21:04 dpdklab
2023-12-13 21:04 dpdklab
2023-12-13 21:03 dpdklab
2023-12-13 21:02 dpdklab
2023-12-13 21:01 dpdklab
2023-12-13 20:59 dpdklab
2023-12-13 20:58 dpdklab
2023-12-13 20:56 dpdklab
2023-12-13 20:56 dpdklab
2023-12-13 20:52 dpdklab
2023-12-13 20:52 dpdklab
2023-12-13 20:46 dpdklab
2023-12-13 20:21 dpdklab
2023-12-13 20:17 dpdklab
2023-12-13 20:17 dpdklab
2023-12-13 20:16 dpdklab
2023-12-13 20:04 dpdklab
2023-12-13 19:35 dpdklab
2023-12-13 19:35 dpdklab
2023-12-13 19:34 dpdklab
2023-12-13 19:33 dpdklab
2023-12-13 19:25 dpdklab
2023-12-13 19:21 dpdklab
2023-12-13 19:19 dpdklab
2023-12-13 19:14 dpdklab
2023-12-13 19:14 dpdklab
2023-12-13 19:12 dpdklab
2023-12-13 19:11 dpdklab
2023-12-13 19:08 dpdklab
2023-12-13 18:53 dpdklab
2023-12-13 18:52 dpdklab
2023-12-13 18:52 dpdklab
2023-12-13 18:49 dpdklab
2023-12-13 18:42 dpdklab
2023-12-13 18:40 dpdklab
2023-12-13 18:40 dpdklab
2023-12-13 18:39 dpdklab
2023-12-13 18:38 dpdklab
2023-12-13 18:32 dpdklab
2023-12-13 18:30 dpdklab
2023-12-13 18:27 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=657a0d91.050a0220.7a9e.ba78SMTPIN_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).