From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw50073-50077 [PATCH] [v4, 1/5] ring: add 64-bit headtail structure
Date: Tue, 29 Jan 2019 16:30:14 -0500 (EST) [thread overview]
Message-ID: <20190129213014.A0086785A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2996 bytes --]
http://dpdk.org/patch/50073
_apply patch file failure_
Submitter: Eads, Gage <gage.eads@intel.com>
Date: Monday, January 28 2019 18:14:03
Applied on: Branch: master
CommitID:a2f9c0d417e3417e2858f2446b08ea27d962b056
Apply patch set 50073-50077 failed:
Configuration done using x86_64-native-linuxapp-gcc
== Build lib
== Build lib/librte_compat
== Build lib/librte_kvargs
== Build lib/librte_eal
== Build lib/librte_eal/common
== Build lib/librte_eal/linuxapp
== Build lib/librte_eal/linuxapp/eal
== Build lib/librte_pci
== Build lib/librte_ring
== Build lib/librte_mempool
CC rte_mempool.o
In file included from /var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring.h:442:0,
from /var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/lib/librte_mempool/rte_mempool.h:50,
from /var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/lib/librte_mempool/rte_mempool.c:34:
/var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring_generic.h: In function ‘__rte_ring_do_nb_enqueue_mp’:
/var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring_generic.h:440:3: error: implicit declaration of function ‘rte_atomic128_cmpset’ [-Werror=implicit-function-declaration]
if (rte_atomic128_cmpset((volatile rte_int128_t *)ring_ptr,
^
/var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring_generic.h:440:3: error: nested extern declaration of ‘rte_atomic128_cmpset’ [-Werror=nested-externs]
/var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring_generic.h:440:3: error: unknown type name ‘rte_int128_t’
/var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring_generic.h:441:8: error: ‘rte_int128_t’ undeclared (first use in this function)
(rte_int128_t *)&old_value,
^
/var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring_generic.h:441:8: note: each undeclared identifier is reported only once for each function it appears in
/var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring_generic.h:441:22: error: expected expression before ‘)’ token
(rte_int128_t *)&old_value,
^
/var/lib/jenkins/workspace/Apply-One-Patch-Set/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring_generic.h:403:35: error: variable ‘new_value’ set but not used [-Werror=unused-but-set-variable]
struct nb_ring_entry old_value, new_value;
^
cc1: all warnings being treated as errors
make[5]: *** [rte_mempool.o] Error 1
make[4]: *** [librte_mempool] 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/4475/
UNH-IOL DPDK Performance Test Lab
next reply other threads:[~2019-01-29 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 21:30 dpdklab [this message]
2019-01-30 13:58 dpdklab
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=20190129213014.A0086785A@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@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).