From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw159605 [PATCH] [v2] cryptodev: add SNOW5G spec
Date: Wed, 07 Jan 2026 18:56:18 -0800 (PST) [thread overview]
Message-ID: <695f1cd2.170a0220.8bde2.0ef6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260106112357.2454990-1-nkaithakadan@marvell.com>
Test-Label: iol-unit-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/159605
_Testing pending_
Submitter: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
Date: Tuesday, January 06 2026 11:23:57
DPDK git baseline: Repo:dpdk-next-crypto
Branch: master
CommitID:cd60dcd503b91956f966a1f6d595b35d256ac00f
159605 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#403561
Test environment and result as below:
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Environment | dpdk_unit_test | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+==============================+================+==============+===========================+==============================+
| CentOS Stream 10 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| CentOS Stream 9 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Debian GNU/Linux 12 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Fedora Linux 40 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Fedora Linux 42 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Fedora Linux 41 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 20.04 | PEND | PASS | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 24.04 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 22.04 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Red Hat Enterprise Linux 9.7 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Debian 12 (arm) | SKIPPED | SKIPPED | PEND | PEND |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
CentOS Stream 10
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20251022 (Red Hat 14.3.1-4)
CentOS Stream 9
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-14)
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 40
Kernel: 5.4
Compiler: clang gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 42
Kernel: 5.4
Compiler: gcc gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)
Fedora Linux 41
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 24.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Ubuntu 22.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
Red Hat Enterprise Linux 9.7
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
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/34800/
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:[~2026-01-08 2:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260106112357.2454990-1-nkaithakadan@marvell.com>
2026-01-06 11:01 ` |SUCCESS| pw159605 [PATCH v2] " qemudev
2026-01-06 11:06 ` qemudev
2026-01-06 11:24 ` checkpatch
2026-01-06 12:25 ` 0-day Robot
2026-01-06 12:25 ` 0-day Robot
2026-01-07 22:35 ` |SUCCESS| pw159605 [PATCH] [v2] " dpdklab
2026-01-07 23:20 ` dpdklab
2026-01-07 23:59 ` dpdklab
2026-01-08 1:14 ` dpdklab
2026-01-08 2:43 ` |PENDING| " dpdklab
2026-01-08 2:56 ` dpdklab [this message]
2026-01-08 3:38 ` |SUCCESS| " dpdklab
2026-01-08 12:39 ` dpdklab
2026-01-08 13:46 ` dpdklab
2026-01-08 19:18 ` dpdklab
2026-01-08 21:21 ` dpdklab
2026-01-08 21:23 ` dpdklab
2026-01-08 21:25 ` dpdklab
2026-01-08 21:25 ` dpdklab
2026-01-08 22:11 ` dpdklab
2026-01-08 22:55 ` dpdklab
2026-01-08 23:15 ` dpdklab
2026-01-08 23:32 ` dpdklab
2026-01-08 23:34 ` dpdklab
2026-01-08 23:35 ` dpdklab
2026-01-08 23:41 ` dpdklab
2026-01-09 0:10 ` dpdklab
2026-01-09 0:11 ` dpdklab
2026-01-09 0:11 ` dpdklab
2026-01-09 23:59 ` 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=695f1cd2.170a0220.8bde2.0ef6SMTPIN_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).