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,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |WARNING| pw135343-135344 [PATCH] [2/2] eal: remove typeof from per
Date: Tue, 19 Dec 2023 13:40:02 -0800 (PST)	[thread overview]
Message-ID: <65820db2.250a0220.0205.ba36SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, December 19 2023 17:27:44 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135343-135344 --> testing fail

Test environment and result as below:

+--------------+----------------------+
| Environment  | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | WARN                 |
+--------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
717 |  if (unlikely(RTE_PER_LCORE(gcm_ops)[s->key_length].init == NULL))
|               ^~~~~~~~~~~~~
[2105/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_cnxk@sta/crypto_cnxk_cnxk_cryptodev_ops.c.o'.
[2106/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_ipsec_mb_ops.c.o'.
[2107/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa_sec@sta/crypto_dpaa_sec_dpaa_sec_raw_dp.c.o'.
[2108/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_chacha_poly.c.o'.
[2109/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_caam_jr@sta/crypto_caam_jr_caam_jr.c.o'.
[2110/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa2_sec@sta/crypto_dpaa2_sec_dpaa2_sec_raw_dp.c.o'.
[2111/2814] Generating rte_net_mlx5.sym_chk with a meson_exe.py custom command.
[2112/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_kasumi.c.o'.
[2113/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_snow3g.c.o'.
[2114/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_zuc.c.o'.
[2115/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ccp@sta/crypto_ccp_ccp_crypto.c.o'.
[2116/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_ipsec_mb@sta/crypto_ipsec_mb_pmd_aesni_mb.c.o'.
[2117/2814] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command.
[2118/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa_sec@sta/crypto_dpaa_sec_dpaa_sec.c.o'.
[2119/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa2_sec@sta/crypto_dpaa2_sec_dpaa2_sec_dpseci.c.o'.
[2120/2814] Compiling C object 'drivers/a715181@@tmp_rte_crypto_cnxk@sta/crypto_cnxk_cn9k_cryptodev_ops.c.o'.
[2121/2814] 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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-19 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 21:40 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-19 21:02 dpdklab
2023-12-19 20:54 dpdklab
2023-12-19 20:51 dpdklab
2023-12-19 20:47 dpdklab
2023-12-19 20: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=65820db2.250a0220.0205.ba36SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=roretzla@linux.microsoft.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).