From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw157207-157208 [PATCH] [v6,2/2] crypto/ipsec-mb: use cons
Date: Thu, 02 Oct 2025 09:09:09 -0700 (PDT) [thread overview]
Message-ID: <68dea3a5.050a0220.8e9f4.ba4dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251002153229.98158-2-kai.ji@intel.com>
Test-Label: iol-unit-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/157208
_Testing pending_
Submitter: Kai Ji <kai.ji@intel.com>
Date: Thursday, October 02 2025 15:32:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:76393b98bf67f94dc6aa23cf5016c32571899261
157207-157208 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#377896
Test environment and result as below:
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_snow3g_autotest | lpm_autotest | cryptodev_sw_zuc_autotest |
+==============================+================+==============================+==============+===========================+
| CentOS Stream 9 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| CentOS Stream 10 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Debian GNU/Linux 12 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Ubuntu 22.04 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora Linux 40 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora Linux 41 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora Linux 42 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Ubuntu 20.04 | PEND | SKIPPED | PASS | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Red Hat Enterprise Linux 9.5 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Ubuntu 24.04 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Debian 12 (arm) | SKIPPED | PEND | SKIPPED | PEND |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
CentOS Stream 9
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
CentOS Stream 10
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
Fedora Linux 40
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 41
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Fedora Linux 42
Kernel: 5.4
Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Red Hat Enterprise Linux 9.5
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 24.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34199/
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-10-02 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251002153229.98158-2-kai.ji@intel.com>
2025-10-02 14:57 ` |SUCCESS| pw157207-157208 [dpdk-dev v6 2/2] crypto/ipsec-mb: use constant-time memory comparison qemudev
2025-10-02 15:02 ` qemudev
2025-10-02 15:33 ` |SUCCESS| pw157208 " checkpatch
2025-10-02 16:04 ` |PENDING| pw157207-157208 [PATCH] [v6,2/2] crypto/ipsec-mb: use cons dpdklab
2025-10-02 16:06 ` |SUCCESS| " dpdklab
2025-10-02 16:09 ` dpdklab [this message]
2025-10-02 16:09 ` dpdklab
2025-10-02 16:16 ` |PENDING| " dpdklab
2025-10-02 16:24 ` |SUCCESS| " dpdklab
2025-10-02 16:26 ` dpdklab
2025-10-02 16:30 ` dpdklab
2025-10-02 16:41 ` |PENDING| " dpdklab
2025-10-02 16:46 ` |SUCCESS| " dpdklab
2025-10-02 16:48 ` dpdklab
2025-10-02 16:50 ` |SUCCESS| pw157208 [dpdk-dev v6 2/2] crypto/ipsec-mb: use constant-time memory comparison 0-day Robot
2025-10-02 16:50 ` 0-day Robot
2025-10-02 16:57 ` |SUCCESS| pw157207-157208 [PATCH] [v6,2/2] crypto/ipsec-mb: use cons dpdklab
2025-10-02 16:59 ` dpdklab
2025-10-02 19:01 ` |WARNING| " 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=68dea3a5.050a0220.8e9f4.ba4dSMTPIN_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).