From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jia.guo@intel.com
Subject: [dpdk-test-report] |FAILURE| pw25935 [PATCH v3 2/2] net/i40e: add hot plug monitor in i40e
Date: 29 Jun 2017 19:25:13 -0700 [thread overview]
Message-ID: <e81775$12ococu@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 8988 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/25935
_Compilation issues_
Submitter: Guo Jia <jia.guo@intel.com>
Date: Thu, 29 Jun 2017 13:01:49 +0800
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:bbe569daa7e99b36d44b12bb3d23ddfbc26d383c
Patch25934-25935 --> compile error
Build Summary: 21 Builds Done, 15 Successful, 6 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: UB1610_64
Kernel Version:4.8.0-22-generic
CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version:gcc (Ubuntu 6.2.0-5ubuntu12) 6.2.0 20161005
Clang Version:NA
x86_64-native-linuxapp-icc
OS: RHEL7.3_64
Kernel Version:3.10.0-514.16.1.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-11)
Clang Version:NA
x86_64-native-linuxapp-icc
OS: FC25_64
Kernel Version:4.8.6-300.fc25.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version:gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1)
Clang Version:NA
x86_64-native-linuxapp-icc
OS: FreeBSD10.3_64
Kernel Version:10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.98-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: 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
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-gcc-debug
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
OS: UB1604_64
Kernel Version:4.4.0-78-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
Failed Build #1:
OS: RHEL7.2_64
Target: x86_64-native-linuxapp-gcc-shared
PMDINFO i40e_ethdev.o.pmd.c LD i40e_ethdev.o PMDINFO i40e_ethdev_vf.o.pmd.c LD i40e_ethdev_vf.o LD librte_pmd_i40e.so.1.1
i40e_ethdev.o: In function `i40e_dev_interrupt_handler':
i40e_ethdev.c:(.text+0xb47d): undefined reference to `rte_uevent_get'
collect2: error: ld returned 1 exit status
Failed Build #2:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-clang
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c:120:19: error: no member named 'uevent_fd' in 'struct rte_intr_handle'
dev->intr_handle.uevent_fd = -1;
~~~~~~~~~~~~~~~~ ^
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c:231:23: error: no member named 'uevent_fd' in 'struct rte_intr_handle'
if (dev->intr_handle.uevent_fd >= 0) {
~~~~~~~~~~~~~~~~ ^
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c:232:26: error: no member named 'uevent_fd' in 'struct rte_intr_handle'
close(dev->intr_handle.uevent_fd);
~~~~~~~~~~~~~~~~ ^
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c:233:20: error: no member named 'uevent_fd' in 'struct rte_intr_handle'
dev->intr_handle.uevent_fd = -1;
~~~~~~~~~~~~~~~~ ^
4 errors generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'eal_common_pci_uio.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'eal' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'bsdapp' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'librte_eal' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:73: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:128: 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:107: recipe for target 'install' failed
Failed Build #3:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-gcc
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c: In function 'pci_uio_map_resource':
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c:120:18: error: 'struct rte_intr_handle' has no member named 'uevent_fd'
dev->intr_handle.uevent_fd = -1;
^
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c: In function 'pci_uio_unmap_resource':
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c:231:22: error: 'struct rte_intr_handle' has no member named 'uevent_fd'
if (dev->intr_handle.uevent_fd >= 0) {
^
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c:232:25: error: 'struct rte_intr_handle' has no member named 'uevent_fd'
close(dev->intr_handle.uevent_fd);
^
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_common_pci_uio.c:233:19: error: 'struct rte_intr_handle' has no member named 'uevent_fd'
dev->intr_handle.uevent_fd = -1;
^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'eal_common_pci_uio.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'eal' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'bsdapp' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'librte_eal' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:73: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:128: 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:107: recipe for target 'install' failed
Failed Build #4:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc-shared
PMDINFO i40e_ethdev.o.pmd.c LD i40e_ethdev.o PMDINFO i40e_ethdev_vf.o.pmd.c LD i40e_ethdev_vf.o LD librte_pmd_i40e.so.1.1
i40e_ethdev.o: In function `i40e_dev_interrupt_handler':
i40e_ethdev.c:(.text+0xb47d): undefined reference to `rte_uevent_get'
collect2: error: ld returned 1 exit status
Failed Build #5:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc-shared
PMDINFO i40e_ethdev.o.pmd.c LD i40e_ethdev.o PMDINFO i40e_ethdev_vf.o.pmd.c LD i40e_ethdev_vf.o LD librte_pmd_i40e.so.1.1
i40e_ethdev.o: In function `i40e_dev_interrupt_handler':
i40e_ethdev.c:(.text+0xa2b1): undefined reference to `rte_uevent_get'
collect2: error: ld returned 1 exit status
/home/patchWorkOrg/compilation/mk/rte.lib.mk:127: recipe for target 'librte_pmd_i40e.so.1.1' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'i40e' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'net' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:73: recipe for target 'drivers' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:128: 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:107: recipe for target 'install' failed
Failed Build #6:
OS: UB1604_64
Target: x86_64-native-linuxapp-gcc-shared
PMDINFO i40e_ethdev.o.pmd.c LD i40e_ethdev.o PMDINFO i40e_ethdev_vf.o.pmd.c LD i40e_ethdev_vf.o LD librte_pmd_i40e.so.1.1
i40e_ethdev.o: In function `i40e_dev_interrupt_handler':
i40e_ethdev.c:(.text+0xa2a1): undefined reference to `rte_uevent_get'
collect2: error: ld returned 1 exit status
/home/patchWorkOrg/compilation/mk/rte.lib.mk:127: recipe for target 'librte_pmd_i40e.so.1.1' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'i40e' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'net' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:73: recipe for target 'drivers' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:128: 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:107: recipe for target 'install' failed
DPDK STV team
reply other threads:[~2017-06-30 2:25 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$12ococu@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jia.guo@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).