From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw157034-157035 [PATCH] [v4,2/2] crypto/ipsec-mb: use cons
Date: Mon, 29 Sep 2025 08:31:34 -0700 (PDT) [thread overview]
Message-ID: <68daa656.050a0220.342dde.3135SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250929145049.153078-2-kai.ji@intel.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/157035
_Functional Testing PASS_
Submitter: Kai Ji <kai.ji@intel.com>
Date: Monday, September 29 2025 14:50:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1d627ea13aeec2bcccf27246e6be2508370d171e
157034-157035 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#247002
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+----------------+--------+
| Test Suite | Result |
+================+========+
| cmdline | PASS |
+----------------+--------+
| rxtx_callbacks | PASS |
+----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34172/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-09-29 15:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250929145049.153078-2-kai.ji@intel.com>
2025-09-29 14:17 ` |SUCCESS| pw157034-157035 [dpdk-dev v4 2/2] crypto/ipsec-mb: use constant-time memory comparison qemudev
2025-09-29 14:22 ` qemudev
2025-09-29 14:49 ` |WARNING| pw157035 " checkpatch
2025-09-29 15:27 ` |PENDING| pw157034-157035 [PATCH] [v4,2/2] crypto/ipsec-mb: use cons dpdklab
2025-09-29 15:27 ` |SUCCESS| " dpdklab
2025-09-29 15:31 ` dpdklab [this message]
2025-09-29 15:46 ` dpdklab
2025-09-29 15:48 ` |PENDING| " dpdklab
2025-09-29 16:01 ` dpdklab
2025-09-29 16:03 ` |SUCCESS| " dpdklab
2025-09-29 16:21 ` dpdklab
2025-09-29 16:22 ` dpdklab
2025-09-29 16:57 ` |FAILURE| pw157035 [dpdk-dev v4 2/2] crypto/ipsec-mb: use constant-time memory comparison 0-day Robot
2025-09-29 17:08 ` |SUCCESS| pw157034-157035 [PATCH] [v4,2/2] crypto/ipsec-mb: use cons dpdklab
2025-09-29 17:15 ` dpdklab
2025-09-29 17:19 ` dpdklab
2025-09-29 17:20 ` dpdklab
2025-09-29 17:20 ` |PENDING| " dpdklab
2025-09-29 17:20 ` |SUCCESS| " dpdklab
2025-09-29 17:20 ` dpdklab
2025-09-29 18:56 ` dpdklab
2025-09-30 0:18 ` dpdklab
2025-09-30 4:35 ` dpdklab
2025-09-30 4:35 ` dpdklab
2025-09-30 4:35 ` dpdklab
2025-10-01 5:00 ` 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=68daa656.050a0220.342dde.3135SMTPIN_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).