automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: |FAILURE| pw157144-157146 [PATCH] [v1,3/3] app/test: add ML crypto t
Date: Tue, 30 Sep 2025 12:18:00 -0700 (PDT)	[thread overview]
Message-ID: <68dc2ce8.050a0220.e47a5.f805SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250930180316.1021-4-gmuthukrishn@marvell.com>

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/157146

_Testing issues_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Tuesday, September 30 2025 18:03:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f3878b615e69a12087a6c5d212723478cfc79c31

157144-157146 --> testing issues

Upstream job id: Windows-Compile-DPDK-Native#31332

Test environment and result as below:

+---------------------+-------------------------+--------------------+-------------------+----------------------+
|     Environment     | dpdk_llvm_clang_compile | dpdk_meson_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+=========================+====================+===================+======================+
| Windows Server 2022 | PASS                    | SKIPPED            | PASS              | PASS                 |
+---------------------+-------------------------+--------------------+-------------------+----------------------+
| Ubuntu 20.04        | SKIPPED                 | PASS               | SKIPPED           | SKIPPED              |
+---------------------+-------------------------+--------------------+-------------------+----------------------+
| FreeBSD 14.2        | SKIPPED                 | FAIL               | SKIPPED           | SKIPPED              |
+---------------------+-------------------------+--------------------+-------------------+----------------------+

==== 20 line log output for FreeBSD 14.2 (dpdk_meson_compile): ====
/usr/local/include/openssl/evp.h:1902:5: note: 'EVP_PKEY_verify_recover_init' declared here
1902 | int EVP_PKEY_verify_recover_init(EVP_PKEY_CTX *ctx);
|     ^
../drivers/crypto/openssl/rte_openssl_pmd.c:4028:19: error: use of undeclared identifier 'OSSL_SIGNATURE_PARAM_MU'
4028 |                         OSSL_PARAM_int(OSSL_SIGNATURE_PARAM_MU, &has_mu),
|                                        ^
../drivers/crypto/openssl/rte_openssl_pmd.c:4042:28: error: use of undeclared identifier 'OSSL_SIGNATURE_PARAM_CONTEXT_STRING'
4042 |                         OSSL_PARAM_octet_string(OSSL_SIGNATURE_PARAM_CONTEXT_STRING,
|                                                 ^
../drivers/crypto/openssl/rte_openssl_pmd.c:4313:12: error: call to undeclared function 'process_openssl_mlkem_op'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration]
4313 |                 retval = process_openssl_mlkem_op(op, sess);
|                          ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
[1676/2137] Linking target drivers/librte_crypto_ionic.so.26.0
[1677/2137] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_rte_cryptodev_scheduler.c.o
[1678/2137] Generating rte_crypto_null.sym_chk with a custom command (wrapped by meson to capture output)
[1679/2137] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_failover.c.o
[1680/2137] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_multicore.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

Ubuntu 20.04
	Kernel: 4.19
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34185/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-09-30 19:18 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250930180316.1021-4-gmuthukrishn@marvell.com>
2025-09-30 17:29 ` |SUCCESS| pw157144-157146 [PATCH v1 3/3] app/test: add ML crypto test vectors qemudev
2025-09-30 17:34 ` qemudev
2025-09-30 18:05 ` |WARNING| pw157146 " checkpatch
2025-09-30 18:34 ` |PENDING| pw157144-157146 [PATCH] [v1,3/3] app/test: add ML crypto t dpdklab
2025-09-30 18:37 ` |SUCCESS| " dpdklab
2025-09-30 18:37 ` |PENDING| " dpdklab
2025-09-30 18:37 ` |FAILURE| " dpdklab
2025-09-30 18:38 ` dpdklab
2025-09-30 18:38 ` dpdklab
2025-09-30 18:48 ` dpdklab
2025-09-30 18:49 ` |PENDING| " dpdklab
2025-09-30 18:52 ` |FAILURE| " dpdklab
2025-09-30 18:54 ` dpdklab
2025-09-30 18:54 ` dpdklab
2025-09-30 18:56 ` dpdklab
2025-09-30 18:58 ` |SUCCESS| " dpdklab
2025-09-30 19:00 ` |FAILURE| " dpdklab
2025-09-30 19:00 ` |SUCCESS| " dpdklab
2025-09-30 19:01 ` dpdklab
2025-09-30 19:03 ` |FAILURE| " dpdklab
2025-09-30 19:07 ` dpdklab
2025-09-30 19:08 ` dpdklab
2025-09-30 19:15 ` dpdklab
2025-09-30 19:18 ` dpdklab [this message]
2025-09-30 19:28 ` dpdklab
2025-09-30 20:39 ` |FAILURE| pw157146 [PATCH v1 3/3] app/test: add ML crypto test vectors 0-day Robot
2025-09-30 21:59 ` |SUCCESS| pw157144-157146 [PATCH] [v1,3/3] app/test: add ML crypto t dpdklab
2025-09-30 22:00 ` dpdklab
2025-10-01  1:56 ` |FAILURE| " dpdklab
2025-10-01  2:06 ` dpdklab
2025-10-01  2:20 ` |PENDING| " dpdklab
2025-10-01  2:36 ` |FAILURE| " dpdklab
2025-10-01  2:50 ` dpdklab
2025-10-01  3:44 ` dpdklab
2025-10-01  4:02 ` dpdklab
2025-10-01  4:18 ` dpdklab
2025-10-01  4:45 ` dpdklab
2025-10-01  5:35 ` dpdklab
2025-10-01  9:06 ` dpdklab
2025-10-01 14:11 ` dpdklab
2025-10-01 14:12 ` dpdklab
2025-10-01 15:46 ` 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=68dc2ce8.050a0220.e47a5.f805SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gmuthukrishn@marvell.com \
    --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).