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| pw149231-149232 [PATCH] [v1,2/2] app/test: add SM4 GCM tes
Date: Fri, 13 Dec 2024 22:08:01 -0800 (PST)	[thread overview]
Message-ID: <675d20c1.050a0220.230ca9.3ac9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241213125850.2714328-2-brian.dooley@intel.com>

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

_Testing issues_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Friday, December 13 2024 12:58:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7df61db6c387703a36306c1aea92225921e2eeb2

149231-149232 --> testing issues

Upstream job id: ACVP-FIPS-testing#8276

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): ====
| ^
cc1: all warnings being treated as errors
[2387/3162] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec_raw_dp.c.o
[2388/3162] Compiling C object drivers/libtmp_rte_crypto_ionic.a.p/crypto_ionic_ionic_crypto_main.c.o
[2389/3162] Compiling C object drivers/libtmp_rte_crypto_ccp.a.p/crypto_ccp_ccp_crypto.c.o
[2390/3162] Generating rte_crypto_caam_jr.pmd.c with a custom command
[2391/3162] Compiling C object drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_private.c.o
[2392/3162] Compiling C object drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_ops.c.o
[2393/3162] Compiling C object drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_kasumi.c.o
[2394/3162] Compiling C object drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_chacha_poly.c.o
[2395/3162] Compiling C object drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_gcm.c.o
[2396/3162] Compiling C object drivers/libtmp_rte_crypto_mlx5.a.p/crypto_mlx5_mlx5_crypto.c.o
[2397/3162] Compiling C object drivers/libtmp_rte_crypto_mlx5.a.p/crypto_mlx5_mlx5_crypto_xts.c.o
[2398/3162] Compiling C object drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_zuc.c.o
[2399/3162] Compiling C object drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_snow3g.c.o
[2400/3162] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec.c.o
[2401/3162] Compiling C object drivers/libtmp_rte_crypto_dpaa2_sec.a.p/crypto_dpaa2_sec_dpaa2_sec_dpseci.c.o
[2402/3162] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn9k_cryptodev_ops.c.o
[2403/3162] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/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/32138/

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2024-12-14  6:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241213125850.2714328-2-brian.dooley@intel.com>
2024-12-13 12:27 ` |SUCCESS| pw149231-149232 [PATCH v1 2/2] app/test: add SM4 GCM tests qemudev
2024-12-13 12:31 ` qemudev
2024-12-13 13:00 ` |SUCCESS| pw149232 " checkpatch
2024-12-13 14:02 ` |FAILURE| " 0-day Robot
2024-12-13 22:31 ` |SUCCESS| pw149231-149232 [PATCH] [v1,2/2] app/test: add SM4 GCM tes dpdklab
2024-12-13 22:35 ` dpdklab
2024-12-13 22:40 ` dpdklab
2024-12-13 23:02 ` dpdklab
2024-12-13 23:09 ` dpdklab
2024-12-14  0:06 ` dpdklab
2024-12-14  0:46 ` |FAILURE| " dpdklab
2024-12-14  0:47 ` |PENDING| " dpdklab
2024-12-14  0:48 ` |FAILURE| " dpdklab
2024-12-14  0:54 ` dpdklab
2024-12-14  1:05 ` |SUCCESS| " dpdklab
2024-12-14  1:27 ` |PENDING| " dpdklab
2024-12-14  2:08 ` |WARNING| " dpdklab
2024-12-14  2:28 ` dpdklab
2024-12-14  2:48 ` |SUCCESS| " dpdklab
2024-12-14  3:37 ` |WARNING| " dpdklab
2024-12-14  4:55 ` |SUCCESS| " dpdklab
2024-12-14  5:36 ` dpdklab
2024-12-14  6:08 ` 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=675d20c1.050a0220.230ca9.3ac9SMTPIN_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).