From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw51085-51099 [PATCH] [01/15] app/testpmd: replace uint with unsigned int
Date: Tue, 12 Mar 2019 09:55:18 -0400 (EDT) [thread overview]
Message-ID: <20190312135519.0595D10480@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Test-Label: Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/51085
_build patch failure_
Submitter: Natanael Copa <ncopa@alpinelinux.org>
Date: Monday, March 11 2019 17:36:48
Applied on: CommitID:610e235a11e49a1e5d55c2804a5bc628e87417f1
Apply patch set 51085-51099 failed:
Configuration done using x86_64-native-linuxapp-gcc
== Build lib
== Build lib/librte_kvargs
== Build lib/librte_eal
== Build lib/librte_eal/common
== Build lib/librte_eal/linuxapp
== Build lib/librte_eal/linuxapp/eal
CC eal_dev.o
/var/lib/jenkins/workspace/Apply-Custom-Patch-Set/dpdk/lib/librte_eal/linuxapp/eal/eal_dev.c: In function ‘sigbus_handler’:
/var/lib/jenkins/workspace/Apply-Custom-Patch-Set/dpdk/lib/librte_eal/linuxapp/eal/eal_dev.c:75:2: error: implicit declaration of function ‘gettid’ [-Werror=implicit-function-declaration]
RTE_LOG(DEBUG, EAL, "Thread[%d] catch SIGBUS, fault address:%p\n",
^
/var/lib/jenkins/workspace/Apply-Custom-Patch-Set/dpdk/lib/librte_eal/linuxapp/eal/eal_dev.c:75:2: error: nested extern declaration of ‘gettid’ [-Werror=nested-externs]
cc1: all warnings being treated as errors
make[7]: *** [eal_dev.o] Error 1
make[6]: *** [eal] Error 2
make[5]: *** [linuxapp] Error 2
make[4]: *** [librte_eal] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [pre_install] Error 2
make: *** [install] Error 2
https://lab.dpdk.org/results/dashboard/patchsets/4836/
UNH-IOL DPDK Performance Test Lab
reply other threads:[~2019-03-12 13:55 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=20190312135519.0595D10480@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).