From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw159646 [PATCH] crypto/openssl: Add support for SHA3 algo
Date: Sun, 11 Jan 2026 20:52:09 -0800 (PST) [thread overview]
Message-ID: <69647df9.050a0220.312d83.8704SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260108130827.2366365-1-emma.finn@intel.com>
Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/159646
_Testing pending_
Submitter: Emma Finn <emma.finn@intel.com>
Date: Thursday, January 08 2026 13:08:27
DPDK git baseline: Repo:dpdk-next-crypto
Branch: master
CommitID:cd60dcd503b91956f966a1f6d595b35d256ac00f
159646 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#455419
Test environment and result as below:
+-------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+===============================+====================+
| Red Hat Enterprise Linux 9.7 | PEND |
+-------------------------------+--------------------+
| Ubuntu 24.04 | PEND |
+-------------------------------+--------------------+
| Red Hat Enterprise Linux 10.1 | PEND |
+-------------------------------+--------------------+
| Debian GNU/Linux 12 | PEND |
+-------------------------------+--------------------+
| Fedora Linux 42 | PEND |
+-------------------------------+--------------------+
| Ubuntu 22.04 | PEND |
+-------------------------------+--------------------+
Red Hat Enterprise Linux 9.7
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
Ubuntu 24.04
Kernel: 5.15
Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Red Hat Enterprise Linux 10.1
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250617 (Red Hat 14.3.1-2)
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 42
Kernel: 5.4
Compiler: gcc gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)
Ubuntu 22.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34867/
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-12 4:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260108130827.2366365-1-emma.finn@intel.com>
2026-01-08 13:01 ` |SUCCESS| pw159646 [PATCH] crypto/openssl: Add support for SHA3 algorithms qemudev
2026-01-08 13:06 ` qemudev
2026-01-08 13:09 ` checkpatch
2026-01-08 14:04 ` 0-day Robot
2026-01-08 14:04 ` 0-day Robot
2026-01-08 18:22 ` |SUCCESS| pw159646 [PATCH] crypto/openssl: Add support for SHA3 algo dpdklab
2026-01-08 18:54 ` dpdklab
2026-01-08 19:08 ` dpdklab
2026-01-08 19:16 ` dpdklab
2026-01-09 4:25 ` dpdklab
2026-01-09 5:19 ` dpdklab
2026-01-09 7:01 ` |PENDING| " dpdklab
2026-01-09 7:52 ` |SUCCESS| " dpdklab
2026-01-10 18:22 ` dpdklab
2026-01-10 18:41 ` dpdklab
2026-01-10 20:44 ` dpdklab
2026-01-12 4:52 ` dpdklab [this message]
2026-01-12 4:54 ` |FAILURE| " dpdklab
2026-01-12 4:56 ` dpdklab
2026-01-12 6:02 ` |SUCCESS| " dpdklab
2026-01-12 6:02 ` dpdklab
2026-01-12 6:02 ` dpdklab
2026-01-12 14:29 ` |FAILURE| " dpdklab
2026-01-12 14:57 ` dpdklab
2026-01-12 14:58 ` dpdklab
2026-01-12 14:59 ` dpdklab
2026-01-12 14:59 ` dpdklab
2026-01-12 15:06 ` 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=69647df9.050a0220.312d83.8704SMTPIN_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).