[dpdk-test-report] |FAILURE| pw21688 [PATCH v4 11/17] event/sw: add support for linking queues to ports

automatic DPDK test reports
 help / color / mirror / Atom feed

From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: harry.van.haaren@intel.com
Subject: [dpdk-test-report] |FAILURE| pw21688 [PATCH v4 11/17] event/sw: add support for linking queues to ports
Date: 10 Mar 2017 14:37:35 -0800	[thread overview]
Message-ID: <e81775$11d5e6p@fmsmga001.fm.intel.com> (raw)

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

Test-Label: Intel-compilation
Test-Status: FAILURE

http://dpdk.org/patch/21688

_Compilation issues_

Submitter: Harry van Haaren <harry.van.haaren@intel.com>
Date: Fri, 10 Mar 2017 19:43:17 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:720dbd63fd5083f8cacd6c59aa3f2651121d562a

Patch21678-21688 --> compile error
Build Summary: 18 Builds Done, 0 Successful, 18 Failures

Test environment and configuration as below:
OS: RHEL7.2_64
    Kernel Version:3.10.0-514.10.2.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.9.13-100.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
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-gcc-debug
OS: UB1604_64
    Kernel Version:4.4.0-64-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-514.10.2.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: RHEL7.2_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^


Failed Build #2:
OS: RHEL7.2_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^


Failed Build #3:
OS: RHEL7.2_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^


Failed Build #4:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-clang
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:25: error: no member named 'inflights' in 'struct sw_evdev'
                rte_atomic32_sub(&sw->inflights, possible_inflights);
                                  ~~  ^
1 error generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #5:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-gcc
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function 'sw_port_setup':
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: 'struct sw_evdev' has no member named 'inflights'
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #6:
OS: FC24_64
Target: x86_64-native-linuxapp-clang
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:25: error: no member named 'inflights' in 'struct sw_evdev'
                rte_atomic32_sub(&sw->inflights, possible_inflights);
                                  ~~  ^
1 error generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #7:
OS: FC24_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #8:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #9:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


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

/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #11:
OS: UB1604_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #12:
OS: UB1604_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #13:
OS: UB1604_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #14:
OS: UB1604_64
Target: x86_64-native-linuxapp-clang
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:25: error: no member named 'inflights' in 'struct sw_evdev'
                rte_atomic32_sub(&sw->inflights, possible_inflights);
                                  ~~  ^
1 error generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'sw_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'sw' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'drivers' 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


Failed Build #15:
OS: CentOS7_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^


Failed Build #16:
OS: CentOS7_64
Target: x86_64-native-linuxapp-clang
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:25: error: no member named 'inflights' in 'struct sw_evdev'
                rte_atomic32_sub(&sw->inflights, possible_inflights);
                                  ~~  ^
1 error generated.


Failed Build #17:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^


Failed Build #18:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c: In function ‘sw_port_setup’:
/home/patchWorkOrg/compilation/drivers/event/sw/sw_evdev.c:159:23: error: ‘struct sw_evdev’ has no member named ‘inflights’
   rte_atomic32_sub(&sw->inflights, possible_inflights);
                       ^


DPDK STV team

                 reply	other threads:[~2017-03-10 22:37 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='e81775$11d5e6p@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=harry.van.haaren@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).