From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw50071[1/1] eal: add 128-bit cmpset (x86-64 only)
Date: 28 Jan 2019 09:38:58 -0800 [thread overview]
Message-ID: <0590c7$3vjsj9@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3437 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/50071
_Compilation issues_
Submitter: Gage Eads <gage.eads@intel.com>
Date: 2019-01-28 17:29:45
Reply_mail: 20190128172945.27251-2-gage.eads@intel.com
DPDK git baseline: Repo:dpdk-master, CommitID: a2f9c0d417e3417e2858f2446b08ea27d962b056
Build Summary: 15 Builds Done, 14 Successful, 1 Failures
Test environment and configuration as below:
OS: FC25
Kernel Version: 4.5.5-300.fc24.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 6.1.1 20160510 (Red Hat 6.1.1-2)
Clang Version: 3.8.0 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-debug
OS: FC24
Kernel Version: 4.11.12-100.fc24.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1)
Clang Version: 3.8.1 (tags/RELEASE_381/final)
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
i686-native-linuxapp-gcc
OS: CENTOS
Kernel Version: 3.10.0-957.1.3.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-36)
Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-clang
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
OS: UB1604
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.10) 5.4.0 20160609
Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
OS: FreeBSD
Kernel Version: 10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.76-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 7.3.0
Clang Version: 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc
*Failed Build #1:
OS: FC24
Target: i686-native-linuxapp-gcc
INSTALL-LIB librte_pmd_dpaa2_qdma.a
CC ifpga_feature_dev.o
CC ifpga_fme.o
CC ifpga_fme_iperf.o
CC ifpga_fme_dperf.o
CC ifpga_fme_error.o
CC ifpga_port.o
CC ifpga_port_error.o
CC opae_hw_api.o
CC opae_ifpga_hw_api.o
CC opae_debug.o
CC ifpga_fme_pr.o
CC ifpga_rawdev.o
--
CC test_pipeline_common.o
make[5]: fork: Resource temporarily unavailable
make[5]: fork: Resource temporarily unavailable
make[5]: fork: Resource temporarily unavailable
make[5]: fork: Resource temporarily unavailable
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/e91c50b024584c6a9e3bbf0d8efc995f/dpdk/mk/rte.subdir.mk:35: recipe for target 'test-eventdev' failed
make[4]: *** [test-eventdev] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/e91c50b024584c6a9e3bbf0d8efc995f/dpdk/mk/rte.sdkbuild.mk:49: recipe for target 'app' failed
make[3]: *** [app] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/e91c50b024584c6a9e3bbf0d8efc995f/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
make[2]: *** [all] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/e91c50b024584c6a9e3bbf0d8efc995f/dpdk/mk/rte.sdkinstall.mk:57: recipe for target 'pre_install' failed
make[1]: *** [pre_install] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/e91c50b024584c6a9e3bbf0d8efc995f/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
make: *** [install] Error 2
DPDK STV team
reply other threads:[~2019-01-28 17:39 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='0590c7$3vjsj9@orsmga001.jf.intel.com' \
--to=sys_stv@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).