From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Brian Dooley <brian.dooley@intel.com>
Subject: |WARNING| pw136587 [PATCH] [v2] crypto/ipsec_mb: use new ipad/opad c
Date: Sun, 11 Feb 2024 12:38:35 -0800 (PST) [thread overview]
Message-ID: <65c9304b.050a0220.489b0.3d51SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/136587
_Testing issues_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Sunday, February 11 2024 19:10:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2b551097b3443ebf662e4d140600a4c9b108e73c
136587 --> testing fail
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | WARN | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED | PASS |
+--------------+----------------------+----------------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:323:2: error: nested extern declaration of 'imb_hmac_ipad_opad' [-Werror=nested-externs]
cc1: all warnings being treated as errors
[2136/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_zuc.c.o'.
[2137/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_snow3g.c.o'.
[2138/2822] Linking static target drivers/librte_crypto_ccp.a.
[2139/2822] Linking target drivers/librte_crypto_ccp.so.24.1.
[2140/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_mlx5@sta/crypto_mlx5_mlx5_crypto_gcm.c.o'.
[2141/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_nitrox@sta/crypto_nitrox_nitrox_qp.c.o'.
[2142/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_nitrox@sta/crypto_nitrox_nitrox_sym_capabilities.c.o'.
[2143/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_nitrox@sta/crypto_nitrox_nitrox_sym.c.o'.
[2144/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_null@sta/crypto_null_null_crypto_pmd_ops.c.o'.
[2145/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_capabilities.c.o'.
[2146/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_nitrox@sta/crypto_nitrox_nitrox_sym_reqmgr.c.o'.
[2147/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_null@sta/crypto_null_null_crypto_pmd.c.o'.
[2148/2822] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command.
[2149/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa_sec@sta/crypto_dpaa_sec_dpaa_sec.c.o'.
[2150/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa2_sec@sta/crypto_dpaa2_sec_dpaa2_sec_dpseci.c.o'.
[2151/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_cnxk@sta/crypto_cnxk_cn9k_cryptodev_ops.c.o'.
[2152/2822] Compiling C object 'drivers/a715181@@tmp_rte_crypto_cnxk@sta/crypto_cnxk_cn10k_cryptodev_ops.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.15.0-91-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29114/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-11 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 20:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-11 20:32 dpdklab
2024-02-11 20:16 dpdklab
2024-02-11 20:09 dpdklab
2024-02-11 20:08 dpdklab
2024-02-11 19:58 dpdklab
2024-02-11 19:56 dpdklab
2024-02-11 19:56 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=65c9304b.050a0220.489b0.3d51SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=brian.dooley@intel.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).