From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Bruce Richardson <bruce.richardson@intel.com>
Subject: |WARNING| pw129740 [PATCH] build: update DPDK to use C11 standard
Date: Mon, 31 Jul 2023 17:17:22 -0700 (PDT) [thread overview]
Message-ID: <64c84f12.250a0220.2db78.c371SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/129740
_Testing issues_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, July 31 2023 10:38:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:12fcafcd62286933e6b167b14856d21f642efa5f
129740 --> 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): ====
../lib/eal/common/eal_common_errno.c:48:8: error: nested extern declaration of 'strerror_r' [-Werror=nested-externs]
cc1: all warnings being treated as errors
[21/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_unix_rte_thread.c.o'.
[22/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_alarm.c.o'.
[23/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_lcore.c.o'.
[24/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_uuid.c.o'.
[25/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_dev.c.o'.
[26/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_devargs.c.o'.
[27/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_memory.c.o'.
[28/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_hugepage_info.c.o'.
[29/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_malloc_elem.c.o'.
[30/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal.c.o'.
[31/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_interrupts.c.o'.
[32/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_fbarray.c.o'.
[33/2727] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry.c.o'.
[34/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_memalloc.c.o'.
[35/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_malloc_heap.c.o'.
[36/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_random.c.o'.
[37/2727] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_malloc.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/27164/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-01 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 0:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-31 12:43 dpdklab
[not found] <20230731103858.1491751-1-bruce.richardson@intel.com>
2023-07-31 10:35 ` qemudev
2023-07-31 10:40 ` checkpatch
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=64c84f12.250a0220.2db78.c371SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--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).