From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw157199-157201 [PATCH] [v3,3/3] app/test: add ML crypto t
Date: Wed, 01 Oct 2025 11:43:15 -0700 (PDT) [thread overview]
Message-ID: <68dd7643.050a0220.1a9098.0e2fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251001175658.2303-4-gmuthukrishn@marvell.com>
Test-Label: iol-unit-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/157201
_Testing pending_
Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Wednesday, October 01 2025 17:56:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2ffda8c2e357662354ee6ddcca769258c33642a9
157199-157201 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#377664
Test environment and result as below:
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| Environment | lpm_autotest | dpdk_unit_test | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest |
+==============================+==============+================+==============================+===========================+
| Ubuntu 20.04 | PASS | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| Ubuntu 22.04 | SKIPPED | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| CentOS Stream 9 | SKIPPED | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| CentOS Stream 10 | SKIPPED | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| Fedora Linux 40 | SKIPPED | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| Debian GNU/Linux 12 | SKIPPED | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| Fedora Linux 41 | SKIPPED | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| Fedora Linux 42 | SKIPPED | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| Red Hat Enterprise Linux 9.5 | SKIPPED | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| Ubuntu 24.04 | SKIPPED | PEND | SKIPPED | SKIPPED |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
| Debian 12 (arm) | SKIPPED | SKIPPED | PEND | PEND |
+------------------------------+--------------+----------------+------------------------------+---------------------------+
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
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)
Fedora Linux 40
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 41
Kernel: 5.4
Compiler: clang 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)
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/34196/
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-01 18:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251001175658.2303-4-gmuthukrishn@marvell.com>
2025-10-01 17:31 ` |SUCCESS| pw157199-157201 [PATCH v3 3/3] app/test: add ML crypto test vectors qemudev
2025-10-01 17:36 ` qemudev
2025-10-01 17:59 ` |WARNING| pw157201 " checkpatch
2025-10-01 18:36 ` |SUCCESS| pw157199-157201 [PATCH] [v3,3/3] app/test: add ML crypto t dpdklab
2025-10-01 18:39 ` |PENDING| " dpdklab
2025-10-01 18:43 ` dpdklab [this message]
2025-10-01 18:44 ` |SUCCESS| " dpdklab
2025-10-01 18:50 ` |FAILURE| pw157201 [PATCH v3 3/3] app/test: add ML crypto test vectors 0-day Robot
2025-10-01 18:51 ` |PENDING| pw157199-157201 [PATCH] [v3,3/3] app/test: add ML crypto t dpdklab
2025-10-01 18:53 ` |SUCCESS| " dpdklab
2025-10-01 18:58 ` dpdklab
2025-10-01 19:00 ` dpdklab
2025-10-01 19:12 ` dpdklab
2025-10-01 19:15 ` dpdklab
2025-10-01 19:20 ` dpdklab
2025-10-01 19:23 ` dpdklab
2025-10-01 19:26 ` dpdklab
2025-10-01 19:33 ` dpdklab
2025-10-01 20:30 ` 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=68dd7643.050a0220.1a9098.0e2fSMTPIN_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).