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
Subject: |WARNING| pw144689-144692 [PATCH] [v2,4/4] doc: updated feature matr
Date: Mon, 30 Sep 2024 15:39:11 -0700 (PDT)	[thread overview]
Message-ID: <66fb288f.050a0220.2cce4.11b9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240930135531.3494777-4-brian.dooley@intel.com>

Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/144692

_Testing issues_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Monday, September 30 2024 13:55:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b50d6c67a3c033a49739a0bd1a132aee6d9e324

144689-144692 --> testing issues

Upstream job id: ACVP-FIPS-testing#7111

Test environment and result as below:

+--------------------+----------------------+----------------------+
|    Environment     | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04       | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04       | SKIPPED              | WARN                 |
+--------------------+----------------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
|                                    IMB_CIPHER_SM4_CBC
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:537:36: note: each undeclared identifier is reported only once for each function it appears in
[2244/2966] Generating rte_crypto_caam_jr.pmd.c with a custom command.
[2245/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_chacha_poly.c.o'.
[2246/2966] Generating rte_crypto_ionic.pmd.c with a custom command.
[2247/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_kasumi.c.o'.
[2248/2966] Generating rte_crypto_ccp.pmd.c with a custom command.
[2249/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_mlx5@sta/crypto_mlx5_mlx5_crypto.c.o'.
[2250/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_mlx5@sta/crypto_mlx5_mlx5_crypto_xts.c.o'.
[2251/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_aesni_gcm.c.o'.
[2252/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_zuc.c.o'.
[2253/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_mlx5@sta/crypto_mlx5_mlx5_crypto_dek.c.o'.
[2254/2966] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command.
[2255/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_mlx5@sta/crypto_mlx5_mlx5_crypto_gcm.c.o'.
[2256/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_snow3g.c.o'.
[2257/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa_sec@sta/crypto_dpaa_sec_dpaa_sec.c.o'.
[2258/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa2_sec@sta/crypto_dpaa2_sec_dpaa2_sec_dpseci.c.o'.
[2259/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_cnxk@sta/crypto_cnxk_cn9k_cryptodev_ops.c.o'.
[2260/2966] 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 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 22.04
	Kernel: 5.15.0-100-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2024-09-30 22:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240930135531.3494777-4-brian.dooley@intel.com>
2024-09-30 13:30 ` |SUCCESS| pw144689-144692 [PATCH v2 4/4] doc: updated feature matrix for AESNI MB PMD qemudev
2024-09-30 13:34 ` qemudev
2024-09-30 13:57 ` |SUCCESS| pw144692 " checkpatch
2024-09-30 14:44 ` |FAILURE| " 0-day Robot
2024-09-30 17:52 ` |SUCCESS| pw144689-144692 [PATCH] [v2,4/4] doc: updated feature matr dpdklab
2024-09-30 17:53 ` dpdklab
2024-09-30 18:03 ` dpdklab
2024-09-30 18:03 ` dpdklab
2024-09-30 18:10 ` dpdklab
2024-09-30 18:15 ` dpdklab
2024-09-30 18:22 ` |PENDING| " dpdklab
2024-09-30 18:24 ` |SUCCESS| " dpdklab
2024-09-30 18:35 ` dpdklab
2024-09-30 18:46 ` |PENDING| " dpdklab
2024-09-30 18:48 ` dpdklab
2024-09-30 19:06 ` |SUCCESS| " dpdklab
2024-09-30 19:15 ` dpdklab
2024-09-30 19:47 ` dpdklab
2024-09-30 20:43 ` dpdklab
2024-09-30 21:12 ` dpdklab
2024-09-30 22:39 ` dpdklab [this message]

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=66fb288f.050a0220.2cce4.11b9SMTPIN_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).