automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw72832-72834 [PATCH] [v4, 1/3] eal: disable function versioning on Windows
Date: Thu,  2 Jul 2020 11:46:52 -0400 (EDT)	[thread overview]
Message-ID: <20200702154652.4309F6D437@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2773 bytes --]

Test-Label: Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/72832

_build patch failure_

Submitter: Fady Bader <fady@mellanox.com>
Date: Thursday, July 02 2020 13:14:07 
Applied on: CommitID:b98447077b0609750c10b84b7b2e7be0c8504fad
Apply patch set 72832-72834 failed:


=========================== WARNING ============================
It is recommended to build DPDK using 'meson' and 'ninja'
See https://doc.dpdk.org/guides/linux_gsg/build_dpdk.html
Building DPDK with 'make' will be deprecated in a future release
================================================================

Configuration done using x86_64-native-linuxapp-gcc

=========================== WARNING ============================
It is recommended to build DPDK using 'meson' and 'ninja'
See https://doc.dpdk.org/guides/linux_gsg/build_dpdk.html
Building DPDK with 'make' will be deprecated in a future release
================================================================

== Build lib
== Build lib/librte_kvargs
== Build lib/librte_telemetry
== 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/include
== Build lib/librte_eal/linux
  CC eal_common_trace.o
__rte_trace_mem_per_thread_alloc is not flagged as internal
but is listed in version map
Please add __rte_internal to the definition of __rte_trace_mem_per_thread_alloc
/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.o' failed
make[6]: *** [eal_common_trace.o] Error 1
/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:51: 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:113: 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:92: recipe for target 'install' failed
make: *** [install] Error 2

https://lab.dpdk.org/results/dashboard/patchsets/11794/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2020-07-02 15:46 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=20200702154652.4309F6D437@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).