From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135209 [PATCH] [v1] crypto/ipsec_mb: use new ipad/opad c
Date: Thu, 14 Dec 2023 11:09:23 -0800 (PST) [thread overview]
Message-ID: <657b52e3.0c0a0220.3def0.64afSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135209
_Testing PASS_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Thursday, December 14 2023 16:41:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135209 --> testing pass
Test environment and result as below:
+--------------------------+----------------+
| Environment | dpdk_unit_test |
+==========================+================+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+----------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+----------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+----------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28631/
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-14 19:09 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 19:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 2:27 dpdklab
2023-12-14 21:35 dpdklab
2023-12-14 21:34 dpdklab
2023-12-14 21:00 dpdklab
2023-12-14 20:58 dpdklab
2023-12-14 20:48 dpdklab
2023-12-14 20:47 dpdklab
2023-12-14 20:46 dpdklab
2023-12-14 20:46 dpdklab
2023-12-14 20:46 dpdklab
2023-12-14 20:44 dpdklab
2023-12-14 20:42 dpdklab
2023-12-14 20:42 dpdklab
2023-12-14 20:41 dpdklab
2023-12-14 20:41 dpdklab
2023-12-14 20:38 dpdklab
2023-12-14 20:36 dpdklab
2023-12-14 20:33 dpdklab
2023-12-14 20:33 dpdklab
2023-12-14 20:31 dpdklab
2023-12-14 20:31 dpdklab
2023-12-14 20:31 dpdklab
2023-12-14 20:29 dpdklab
2023-12-14 20:29 dpdklab
2023-12-14 20:28 dpdklab
2023-12-14 20:27 dpdklab
2023-12-14 20:27 dpdklab
2023-12-14 20:26 dpdklab
2023-12-14 20:25 dpdklab
2023-12-14 20:21 dpdklab
2023-12-14 19:59 dpdklab
2023-12-14 19:58 dpdklab
2023-12-14 19:50 dpdklab
2023-12-14 19:49 dpdklab
2023-12-14 19:46 dpdklab
2023-12-14 19:44 dpdklab
2023-12-14 19:43 dpdklab
2023-12-14 19:43 dpdklab
2023-12-14 19:31 dpdklab
2023-12-14 19:30 dpdklab
2023-12-14 19:28 dpdklab
2023-12-14 19:27 dpdklab
2023-12-14 19:27 dpdklab
2023-12-14 19:26 dpdklab
2023-12-14 19:00 dpdklab
2023-12-14 18:53 dpdklab
2023-12-14 18:53 dpdklab
2023-12-14 18:52 dpdklab
2023-12-14 18:52 dpdklab
2023-12-14 18:51 dpdklab
2023-12-14 18:50 dpdklab
2023-12-14 18:50 dpdklab
2023-12-14 18:49 dpdklab
2023-12-14 18:48 dpdklab
2023-12-14 18:47 dpdklab
2023-12-14 18:39 dpdklab
2023-12-14 18:39 dpdklab
2023-12-14 18:39 dpdklab
2023-12-14 18:37 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=657b52e3.0c0a0220.3def0.64afSMTPIN_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).