From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw155006 [PATCH] ethdev: fix shadow variable definition
Date: Thu, 10 Jul 2025 06:10:43 -0700 (PDT) [thread overview]
Message-ID: <686fbbd3.050a0220.2304fb.573fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250703172407.116249-1-stephen@networkplumber.org>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/155006
_Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, July 03 2025 17:24:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ba982f9a1ca9b96ed0394b764f1523d482e963a2
155006 --> testing issues
Upstream job id: ACVP-FIPS-testing#10459
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): ====
862 | void *start, *aligned_start, *end, *aligned_end;
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
[40/3569] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_trace_ctf.c.o
[41/3569] Compiling C object lib/librte_eal.a.p/eal_common_rte_keepalive.c.o
[42/3569] Compiling C object lib/librte_eal.a.p/eal_unix_eal_file.c.o
[43/3569] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_trace_utils.c.o
[44/3569] Compiling C object lib/librte_telemetry.a.p/telemetry_telemetry.c.o
[45/3569] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_proc.c.o
[46/3569] Generating log.sym_chk with a custom command (wrapped by meson to capture output)
[47/3569] Compiling C object lib/librte_eal.a.p/eal_common_malloc_mp.c.o
[48/3569] Compiling C object lib/librte_eal.a.p/eal_unix_eal_filesystem.c.o
[49/3569] Compiling C object lib/librte_eal.a.p/eal_common_hotplug_mp.c.o
[50/3569] Compiling C object lib/librte_eal.a.p/eal_unix_eal_unix_timer.c.o
[51/3569] Compiling C object lib/librte_eal.a.p/eal_common_rte_service.c.o
[52/3569] Compiling C object lib/librte_eal.a.p/eal_unix_eal_firmware.c.o
[53/3569] Compiling C object lib/librte_net.so.25.2.p/net_rte_arp.c.o
[54/3569] Compiling C object lib/librte_eal.a.p/eal_unix_eal_unix_memory.c.o
[55/3569] Compiling C object lib/librte_eal.a.p/eal_unix_eal_unix_thread.c.o
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33589/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-07-10 13:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250703172407.116249-1-stephen@networkplumber.org>
2025-07-03 16:49 ` |SUCCESS| " qemudev
2025-07-03 16:53 ` qemudev
2025-07-03 17:24 ` checkpatch
2025-07-09 16:42 ` |FAILURE| " dpdklab
2025-07-09 18:33 ` dpdklab
2025-07-09 18:33 ` |SUCCESS| " dpdklab
2025-07-09 18:38 ` dpdklab
2025-07-09 18:38 ` |WARNING| " dpdklab
2025-07-09 18:38 ` dpdklab
2025-07-09 18:39 ` dpdklab
2025-07-09 18:39 ` dpdklab
2025-07-09 18:39 ` dpdklab
2025-07-09 18:39 ` dpdklab
2025-07-09 18:39 ` dpdklab
2025-07-09 18:43 ` |SUCCESS| " dpdklab
2025-07-09 19:01 ` |FAILURE| " dpdklab
2025-07-09 19:01 ` dpdklab
2025-07-09 19:02 ` dpdklab
2025-07-09 19:02 ` dpdklab
2025-07-09 19:04 ` dpdklab
2025-07-09 19:05 ` |SUCCESS| " dpdklab
2025-07-09 19:06 ` dpdklab
2025-07-09 19:06 ` dpdklab
2025-07-09 19:10 ` |FAILURE| " dpdklab
2025-07-09 19:23 ` |WARNING| " dpdklab
2025-07-10 2:53 ` |FAILURE| " dpdklab
2025-07-10 3:21 ` dpdklab
2025-07-10 8:01 ` dpdklab
2025-07-10 8:07 ` dpdklab
2025-07-10 13:10 ` 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=686fbbd3.050a0220.2304fb.573fSMTPIN_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).