From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw66851-66882 [PATCH] [v1, 01/32] eal: introduce API for getting thread name
Date: Wed, 18 Mar 2020 15:28:42 -0400 (EDT) [thread overview]
Message-ID: <20200318192842.B4B226D54D@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3669 bytes --]
Test-Label: Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/66851
_build patch failure_
Submitter: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Date: Wednesday, March 18 2020 19:02:10
Applied on: CommitID:61669ecb921fff821db11d81557fa0449a7eb79c
Apply patch set 66851-66882 failed:
Configuration done using x86_64-native-linuxapp-gcc
== Build lib
== Build lib/librte_kvargs
== Build lib/librte_eal
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/toolchain/gcc/rte.toolchain-compat.mk:30: AVX512 support disabled because of binutils 2.30. See Bug 97
== Build lib/librte_eal/common
== Build lib/librte_eal/linux
== Build lib/librte_eal/linux/eal
CC eal_common_trace_ctf.o
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/lib/librte_eal/common/eal_common_trace_ctf.c:16:21: error: expected declaration specifiers or ‘...’ before numeric constant
__rte_format_printf(2, 0)
^
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/lib/librte_eal/common/eal_common_trace_ctf.c:16:24: error: expected declaration specifiers or ‘...’ before numeric constant
__rte_format_printf(2, 0)
^
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/lib/librte_eal/common/eal_common_trace_ctf.c: In function ‘meta_data_type_emit’:
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/lib/librte_eal/common/eal_common_trace_ctf.c:65:7: error: implicit declaration of function ‘metadata_printf’; did you mean ‘obstack_printf’? [-Werror=implicit-function-declaration]
rc = metadata_printf(&str,
^~~~~~~~~~~~~~~
obstack_printf
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/lib/librte_eal/common/eal_common_trace_ctf.c:65:7: error: nested extern declaration of ‘metadata_printf’ [-Werror=nested-externs]
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/lib/librte_eal/common/eal_common_trace_ctf.c: At top level:
cc1: error: unrecognized command line option ‘-Wno-address-of-packed-member’ [-Werror]
cc1: all warnings being treated as errors
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target 'eal_common_trace_ctf.o' failed
make[7]: *** [eal_common_trace_ctf.o] Error 1
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.subdir.mk:35: recipe for target 'eal' failed
make[6]: *** [eal] Error 2
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.subdir.mk:35: recipe for target 'linux' failed
make[5]: *** [linux] Error 2
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.subdir.mk:35: recipe for target 'librte_eal' failed
make[4]: *** [librte_eal] Error 2
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.sdkbuild.mk:46: recipe for target 'lib' failed
make[3]: *** [lib] Error 2
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.sdkroot.mk:98: recipe for target 'all' failed
make[2]: *** [all] Error 2
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.sdkinstall.mk:60: recipe for target 'pre_install' failed
make[1]: *** [pre_install] Error 2
/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/mk/rte.sdkroot.mk:77: recipe for target 'install' failed
make: *** [install] Error 2
https://lab.dpdk.org/results/dashboard/patchsets/10033/
UNH-IOL DPDK Community Lab
reply other threads:[~2020-03-18 19:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200318192842.B4B226D54D@noxus.dpdklab.iol.unh.edu \
--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).