automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com
Subject: [dpdk-test-report] |FAILURE| pw19936 [PATCH RFCv2 3/4] ring: allow common ring to use 8 or 16 byte values
Date: 24 Jan 2017 04:15:27 -0800	[thread overview]
Message-ID: <e624e2$10caujs@orsmga001.jf.intel.com> (raw)

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

Test-Label: Intel compilation
Test-Status: FAILURE

http://dpdk.org/patch/19936

_Compilation issues_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tue, 24 Jan 2017 10:39:34 +0000
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:61207d014fc906302a184ae2f779b54ccfd0cd4c

Patch19934-19936 --> compile error
Build Summary: 18 Builds Done, 17 Successful, 1 Failures

Test environment and configuration as below:
OS: RHEL7.2_64
    Kernel Version:3.10.0-327.el7.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
    GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
    Clang Version:3.4.2
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc-shared
OS: FreeBSD10.3_64
    Kernel Version:10.3-RELEASE
    CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.97-MHz K8-class CPU)
    GCC Version:gcc (FreeBSD Ports Collection) 4.8.5
    Clang Version:3.4.1
    x86_64-native-bsdapp-clang
    x86_64-native-bsdapp-gcc
OS: FC24_64
    Kernel Version:4.8.6-201.fc24.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
    GCC Version:gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
    Clang Version:3.8.0
    x86_64-native-linuxapp-clang
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc-debug
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-gcc
OS: UB1604_64
    Kernel Version:4.4.0-53-generic
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
    GCC Version:gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
    Clang Version:3.8.0
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-clang
OS: CentOS7_64
    Kernel Version:3.10.0-327.el7.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
    GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
    Clang Version:3.4.2
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-clang
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-gcc

Failed Build #1:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc-debug

In file included from /home/patchWorkOrg/compilation/lib/librte_ring/rte_common_ring.c:74:0:
/home/patchWorkOrg/compilation/lib/librte_ring/rte_common_ring.c: In function ‘rte_common_ring_init’:
/home/patchWorkOrg/compilation/lib/librte_ring/rte_common_ring.c:137:27: error: invalid application of ‘sizeof’ to incomplete type ‘struct rte_common_ring_debug_stats’
  RTE_BUILD_BUG_ON((sizeof(struct rte_common_ring_debug_stats) &
                           ^
/home/patchWorkOrg/compilation/x86_64-native-linuxapp-gcc/include/rte_common.h:208:30: note: in definition of macro ‘RTE_BUILD_BUG_ON’
  ((void)sizeof(char[1 - 2*!!(condition)]));   \
                              ^~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_ring/rte_common_ring.c:137:27: error: invalid application of ‘sizeof’ to incomplete type ‘struct rte_common_ring_debug_stats’
  RTE_BUILD_BUG_ON((sizeof(struct rte_common_ring_debug_stats) &
                           ^
/home/patchWorkOrg/compilation/x86_64-native-linuxapp-gcc/include/rte_common.h:209:6: note: in definition of macro ‘RTE_BUILD_BUG_ON’
  if (condition)                               \
      ^~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_ring/rte_common_ring.c: In function ‘rte_common_ring_dump’:
/home/patchWorkOrg/compilation/lib/librte_ring/rte_common_ring.c:291:37: error: storage size of ‘sum’ isn’t known
  struct rte_common_ring_debug_stats sum;
                                     ^~~
/home/patchWorkOrg/compilation/lib/librte_ring/rte_common_ring.c:291:37: warning: unused variable ‘sum’ [-Wunused-variable]
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'rte_common_ring.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_ring' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:126: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:101: recipe for target 'install' failed


DPDK STV team

                 reply	other threads:[~2017-01-24 12:15 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='e624e2$10caujs@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=bruce.richardson@intel.com \
    --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).