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| pw152790 [PATCH] [v3] event/dlb2: consolidate AVX512 and S
Date: Mon, 07 Apr 2025 07:35:24 -0700 (PDT)	[thread overview]
Message-ID: <67f3e2ac.050a0220.2ed372.2e9bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250407091925.3057365-1-tirthendu.sarkar@intel.com>

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

_Testing issues_

Submitter: Tirthendu Sarkar <tirthendu.sarkar@intel.com>
Date: Monday, April 07 2025 09:19:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e30e194c4d06cf9b0e93f9f0f2a289bef96abc1a

152790 --> testing issues

Upstream job id: ACVP-FIPS-testing#9471

Test environment and result as below:

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

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
../drivers/event/dlb2/dlb2_avx512.c:28:16: error: incompatible types when initializing type '__m512i' {aka '__vector(8) long long int'} using type 'int'
cc1: all warnings being treated as errors
[2928/3510] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn20k_deq_all_offload.c.o
[2929/3510] Generating rte_event_dlb2_map with a custom command
[2930/3510] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn20k_tx_all_offload.c.o
[2931/3510] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn20k_worker.c.o
[2932/3510] Compiling C object drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_dlb2_iface.c.o
[2933/3510] Compiling C object drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_dlb2_xstats.c.o
[2934/3510] Compiling C object drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_rte_pmd_dlb2.c.o
[2935/3510] Compiling C object drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_dlb2_sse.c.o
[2936/3510] Compiling C object drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_pf_dlb2_main.c.o
[2937/3510] Compiling C object drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_pf_dlb2_pf.c.o
[2938/3510] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_eventdev.c.o
[2939/3510] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn20k_eventdev.c.o
[2940/3510] Compiling C object drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_dlb2_selftest.c.o
[2941/3510] Compiling C object drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_dlb2.c.o
[2942/3510] Compiling C object drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_pf_base_dlb2_resource.c.o
[2943/3510] Compiling C object drivers/libtmp_rte_crypto_octeontx.a.p/crypto_octeontx_otx_cryptodev_ops.c.o
[2944/3510] 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 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/32953/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-04-07 14:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250407091925.3057365-1-tirthendu.sarkar@intel.com>
2025-04-07  8:53 ` |SUCCESS| pw152790 [PATCH v3] event/dlb2: consolidate AVX512 and SSE changes qemudev
2025-04-07  8:57 ` qemudev
2025-04-07  9:19 ` |WARNING| " checkpatch
2025-04-07 10:22 ` |SUCCESS| " 0-day Robot
2025-04-07 14:09 ` |SUCCESS| pw152790 [PATCH] [v3] event/dlb2: consolidate AVX512 and S dpdklab
2025-04-07 14:10 ` dpdklab
2025-04-07 14:15 ` dpdklab
2025-04-07 14:19 ` |PENDING| " dpdklab
2025-04-07 14:20 ` |SUCCESS| " dpdklab
2025-04-07 14:32 ` dpdklab
2025-04-07 14:35 ` dpdklab [this message]
2025-04-07 14:41 ` |FAILURE| " dpdklab
2025-04-07 14:42 ` |PENDING| " dpdklab
2025-04-07 14:45 ` |SUCCESS| " dpdklab
2025-04-07 14:46 ` |FAILURE| " dpdklab
2025-04-07 14:57 ` |WARNING| " dpdklab
2025-04-07 15:04 ` |SUCCESS| " dpdklab
2025-04-07 15:06 ` dpdklab
2025-04-07 15:06 ` |WARNING| " dpdklab
2025-04-07 15:07 ` |SUCCESS| " dpdklab
2025-04-07 15:09 ` |FAILURE| " dpdklab
2025-04-07 15:18 ` |WARNING| " dpdklab
2025-04-07 15:22 ` dpdklab
2025-04-07 16:29 ` |FAILURE| " dpdklab
2025-04-07 16:32 ` dpdklab
2025-04-07 16:34 ` dpdklab
2025-04-07 16:45 ` dpdklab
2025-04-07 17:32 ` |SUCCESS| " dpdklab
2025-04-07 17:36 ` 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=67f3e2ac.050a0220.2ed372.2e9bSMTPIN_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).