From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nipun.gupta@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw38615 [PATCH 5/9 v3] raw/dpaa2_qdma: introduce the DPAA2 QDMA driver
Date: 03 May 2018 17:02:20 -0700 [thread overview]
Message-ID: <ca5293$1hqrf0@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3514 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38615
_Compilation issues_
Submitter: Nipun Gupta <nipun.gupta@nxp.com>
Date: Fri, 20 Apr 2018 16:01:03 +0530
DPDK git baseline: Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Patch38611-38615 --> compile error
Build Summary: 14 Builds Done, 11 Successful, 3 Failures
Test environment and configuration as below:
OS: FreeBSD10.3_64
Kernel Version:10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.96-MHz K8-class CPU)
GCC Version:gcc (FreeBSD Ports Collection) 4.8.5
Clang Version:3.4.1
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-debug
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
OS: UB1604_64
Kernel Version:4.4.0-81-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-clang
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-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-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
Failed Build #1:
OS: CentOS7_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/raw/dpaa2_qdma/dpaa2_qdma.c:36:1: error: missing initializer for field ‘dev_info_get’ of ‘const struct rte_rawdev_ops’ [-Werror=missing-field-initializers]
};
^
In file included from /home/patchWorkOrg/compilation/drivers/raw/dpaa2_qdma/dpaa2_qdma.c:12:0:
/home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_rawdev_pmd.h:491:20: note: ‘dev_info_get’ declared here
rawdev_info_get_t dev_info_get;
^
cc1: all warnings being treated as errors
Failed Build #2:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/raw/dpaa2_qdma/dpaa2_qdma.c:36:1: error: missing initializer for field ‘dev_info_get’ of ‘const struct rte_rawdev_ops’ [-Werror=missing-field-initializers]
};
^
In file included from /home/patchWorkOrg/compilation/drivers/raw/dpaa2_qdma/dpaa2_qdma.c:12:0:
/home/patchWorkOrg/compilation/x86_64-native-linuxapp-gcc/include/rte_rawdev_pmd.h:491:20: note: ‘dev_info_get’ declared here
rawdev_info_get_t dev_info_get;
^
cc1: all warnings being treated as errors
Failed Build #3:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc-shared
/home/patchWorkOrg/compilation/drivers/raw/dpaa2_qdma/dpaa2_qdma.c:36:1: error: missing initializer for field ‘dev_info_get’ of ‘const struct rte_rawdev_ops’ [-Werror=missing-field-initializers]
};
^
In file included from /home/patchWorkOrg/compilation/drivers/raw/dpaa2_qdma/dpaa2_qdma.c:12:0:
/home/patchWorkOrg/compilation/x86_64-native-linuxapp-gcc/include/rte_rawdev_pmd.h:491:20: note: ‘dev_info_get’ declared here
rawdev_info_get_t dev_info_get;
^
cc1: all warnings being treated as errors
DPDK STV team
reply other threads:[~2018-05-04 0:02 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='ca5293$1hqrf0@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=nipun.gupta@nxp.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).