From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw57567[19.11, V3, 12/12] drivers/crypto/octeontx: enable unbinding for the OcteonTx crypto engines
Date: 08 Aug 2019 02:23:43 -0700 [thread overview]
Message-ID: <ee68f5$7mlk1g@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 12024 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/57567
_Compilation issues_
Submitter: Thierry Herbelot <thierry.herbelot@6wind.com>
Date: 2019-08-08 08:22:17
Reply_mail: 646b6286d102c92dafb3d06553fd4272ed17c41d.1565252336.git.thierry.herbelot@6wind.com
DPDK git baseline: Repo:dpdk, CommitID: de4473d911323ae1d26581c2f85abee5d1aaeb81
Makefile build Summary: 22 Builds Done, 21 Successful, 1 Failures
Meson build Summary: 8 Builds Done, 7 Successful, 1 Failures
+==============================================+===========+==========+
| Makefile | Meson | Document |
+--------------+------+-------+------+------------+-----------+-----------+----------+
| os | gcc | clang | icc | gcc+shared | gcc+debug | gcc/clang | pdf/html |
+--------------+------+-------+------+------------+-----------+-----------+----------+
| RHEL76-64 | pass | | | | | | |
| CENTOS76-64 | pass | | | | | | |
| UB1804-64 | pass | pass | pass | | | pass | pass |
| UB1604-32 | FAIL | | | | | FAIL | |
| UB1904-64 | pass | | | | | | |
| UB1604-64 | pass | pass | | | | | |
| FC30-64 | pass | pass | | | | pass | |
| WIN10-64 | | | | | | pass | |
| FreeBSD12-64 | pass | pass | | pass | pass | pass | |
| RHEL80-64 | pass | pass | pass | pass | pass | pass | |
| SUSE15-64 | pass | pass | | | | pass | |
+--------------+------+-------+------+------------+-----------+-----------+----------+
Test environment and configuration as below:
** Makefile build **
OS: RHEL76-64
Kernel Version: 3.10.0-957.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-36)
Clang Version: NA
x86_64-native-linuxapp-gcc
OS: CENTOS76-64
Kernel Version: 3.10.0-957.10.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-36)
Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-gcc
OS: UB1804-64
Kernel Version: 4.15.0-20-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
Clang Version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
x86_64-native-linuxapp-icc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
OS: UB1904-64
Kernel Version: 5.0.0-13-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (Ubuntu 8.3.0-6ubuntu1) 8.3.0
Clang Version: 8.0.0-3 (tags/RELEASE_800/final)
x86_64-native-linuxapp-gcc
OS: UB1604-32
Kernel Version: 4.4.0-131-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
i686-native-linuxapp-gcc
OS: UB1604-64
Kernel Version: 4.4.0-47-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-clang
x86_64-native-linuxapp-gcc
OS: FC30-64
Kernel Version: 5.1.7-300.fc30.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 9.1.1 20190503 (Red Hat 9.1.1-1)
Clang Version: 8.0.0 (Fedora 8.0.0-1.fc30)
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
OS: FreeBSD12-64
Kernel Version: 12.0-RC3
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.98-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 7.3.0
Clang Version: 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1)
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc+debug
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-gcc
OS: RHEL80-64
Kernel Version: 4.18.0-80.el8.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 8.2.1 20180905 (Red Hat 8.2.1-3)
Clang Version: NA
x86_64-native-linuxapp-gcc+debug
x86_64-native-linuxapp-icc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc+shared
x86_64-native-linuxapp-gcc
OS: SUSE15-64
Kernel Version: 4.12.14-lp150.11-default
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (SUSE Linux) 7.3.1 20180323 [gcc-7-branch revision 258812]
Clang Version: 5.0.1 (tags/RELEASE_501/final 312548)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
** Meson build **
OS: UB1804-64
Kernel Version: 4.15.0-20-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
Clang Version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
x86_64-native-linuxapp-doc
build-gcc-static
build-gcc-shared
build-clang-static
build-clang-shared
build-x86-default
OS: UB1604-32
Kernel Version: 4.4.0-131-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
build-gcc-static
build-gcc-shared
build-clang-static
build-clang-shared
build-x86-default
OS: FC30-64
Kernel Version: 5.0.9-301.fc30.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 9.1.1 20190503 (Red Hat 9.1.1-1)
Clang Version: 8.0.0 (Fedora 8.0.0-1.fc30)
build-gcc-static
build-gcc-shared
build-clang-static
build-clang-shared
build-x86-default
OS: WIN10-64
Kernel Version: N/A
CPU info: N/A
GCC Version: N/A
Clang Version: Clang 8.0.0
x86_64-windows-clang
OS: FreeBSD12-64
Kernel Version: 12.0-RC3
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.99-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 7.3.0
Clang Version: 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1)
build-gcc-static
build-gcc-shared
build-clang-static
build-clang-shared
build-x86-default
OS: RHEL80-64
Kernel Version: 4.18.0-80.el8.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 8.2.1 20180905 (Red Hat 8.2.1-3)
Clang Version: NA
build-gcc-static
build-gcc-shared
build-x86-default
OS: SUSE15-64
Kernel Version: 4.12.14-lp150.11-default
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (SUSE Linux) 7.3.1 20180323 [gcc-7-branch revision 258812]
Clang Version: 5.0.1 (tags/RELEASE_501/final 312548)
build-gcc-static
build-gcc-shared
build-clang-static
build-clang-shared
build-x86-default
*Make Build Failed #1:
OS: UB1604-32
Target: i686-native-linuxapp-gcc
CC virtio_rxtx.o
CC axgbe_i2c.o
/tmp/UB1604-32_K4.4.0_GCC5.4.0/i686-native-linuxapp-gcc/3f8033c6270b43689223c53b9d2455c7/dpdk/drivers/crypto/dpaa_sec/dpaa_sec.c: At top level:
cc1: error: unrecognized command line option ‘-Wno-address-of-packed-member’ [-Werror]
cc1: all warnings being treated as errors
/tmp/UB1604-32_K4.4.0_GCC5.4.0/i686-native-linuxapp-gcc/3f8033c6270b43689223c53b9d2455c7/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target 'dpaa_sec.o' failed
make[6]: *** [dpaa_sec.o] Error 1
/tmp/UB1604-32_K4.4.0_GCC5.4.0/i686-native-linuxapp-gcc/3f8033c6270b43689223c53b9d2455c7/dpdk/mk/rte.subdir.mk:35: recipe for target 'dpaa_sec' failed
make[5]: *** [dpaa_sec] Error 2
make[5]: *** Waiting for unfinished jobs....
CC axgbe_rxtx.o
CC axgbe_rxtx_vec_sse.o
CC ark_pktgen.o
CC ark_rqp.o
--
AR librte_pmd_octeontx_crypto.a
INSTALL-LIB librte_pmd_octeontx_crypto.a
CC cxgbe_filter.o
CC dpaa_rxtx.o
make[6]: warning: Clock skew detected. Your build may be incomplete.
/tmp/UB1604-32_K4.4.0_GCC5.4.0/i686-native-linuxapp-gcc/3f8033c6270b43689223c53b9d2455c7/dpdk/mk/rte.subdir.mk:35: recipe for target 'crypto' failed
make[4]: *** [crypto] Error 2
make[4]: *** Waiting for unfinished jobs....
CC cxgbe_flow.o
CC dpaa2_ethdev.o
CC e1000_82542.o
PMDINFO ena_ethdev.o.pmd.c
--
AR librte_pmd_ixgbe.a
INSTALL-LIB librte_pmd_ixgbe.a
make[6]: warning: Clock skew detected. Your build may be incomplete.
AR librte_pmd_qede.a
INSTALL-LIB librte_pmd_qede.a
/tmp/UB1604-32_K4.4.0_GCC5.4.0/i686-native-linuxapp-gcc/3f8033c6270b43689223c53b9d2455c7/dpdk/mk/rte.sdkbuild.mk:46: recipe for target 'drivers' failed
make[3]: *** [drivers] Error 2
/tmp/UB1604-32_K4.4.0_GCC5.4.0/i686-native-linuxapp-gcc/3f8033c6270b43689223c53b9d2455c7/dpdk/mk/rte.sdkroot.mk:98: recipe for target 'all' failed
make[2]: *** [all] Error 2
/tmp/UB1604-32_K4.4.0_GCC5.4.0/i686-native-linuxapp-gcc/3f8033c6270b43689223c53b9d2455c7/dpdk/mk/rte.sdkinstall.mk:60: recipe for target 'pre_install' failed
make[1]: *** [pre_install] Error 2
/tmp/UB1604-32_K4.4.0_GCC5.4.0/i686-native-linuxapp-gcc/3f8033c6270b43689223c53b9d2455c7/dpdk/mk/rte.sdkroot.mk:77: recipe for target 'install' failed
make: *** [install] Error 2
*Meson Build Failed #1:
OS: UB1604-32
Target:build-gcc-static
FAILED: drivers/a715181@@tmp_rte_pmd_dpaa_sec@sta/crypto_dpaa_sec_dpaa_sec.c.o
gcc -Idrivers/a715181@@tmp_rte_pmd_dpaa_sec@sta -Idrivers -I../drivers -Idrivers/crypto/dpaa_sec -I../drivers/crypto/dpaa_sec -Idrivers/crypto/dpaa_sec/../dpaa2_sec/ -I../drivers/crypto/dpaa_sec/../dpaa2_sec/ -Ilib/librte_cryptodev -I../lib/librte_cryptodev -I. -I../ -Iconfig -I../config -Ilib/librte_eal/common/include -I../lib/librte_eal/common/include -I../lib/librte_eal/linux/eal/include -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal/common/include/arch/x86 -I../lib/librte_eal/common/include/arch/x86 -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Idrivers/bus/dpaa -I../drivers/bus/dpaa -I../drivers/bus/dpaa/include -I../drivers/bus/dpaa/base/qbman -Idrivers/common/dpaax -I../drivers/common/dpaax -Ilib/librte_eventdev -I../lib/librte_eventdev -Ilib/librte_ethdev -I../lib/librte_ethdev -Ilib/librte_net -I../lib/librte_net -Ilib/librte_meter -I../lib/librte_meter -Ilib/librte_hash -I../lib/librte_hash -Ilib/librte_timer -I../lib/librte_timer -Ilib/librte_security -I../lib/librte_security -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include rte_config.h -Wunused-parameter -Wsign-compare -Wcast-qual -Wno-pointer-to-int-cast -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -MD -MQ 'drivers/a715181@@tmp_rte_pmd_dpaa_sec@sta/crypto_dpaa_sec_dpaa_sec.c.o' -MF 'drivers/a715181@@tmp_rte_pmd_dpaa_sec@sta/crypto_dpaa_sec_dpaa_sec.c.o.d' -o 'drivers/a715181@@tmp_rte_pmd_dpaa_sec@sta/crypto_dpaa_sec_dpaa_sec.c.o' -c ../drivers/crypto/dpaa_sec/dpaa_sec.c
../drivers/crypto/dpaa_sec/dpaa_sec.c: In function ‘dpaa_mem_vtop’:
../drivers/crypto/dpaa_sec/dpaa_sec.c:105:37: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
dpaax_iova_table_update(ms->iova, (void *)ms->addr_64, ms->len);
^
cc1: all warnings being treated as errors
[1088/1656] Compiling C object 'drivers/a715181@@tmp_rte_pmd_crypto_scheduler@sta/crypto_scheduler_scheduler_pkt_size_distr.c.o'.
[1089/1656] Compiling C object 'drivers/a715181@@tmp_rte_pmd_dpaa2_sec@sta/crypto_dpaa2_sec_dpaa2_sec_dpseci.c.o'.
[1090/1656] Compiling C object 'drivers/a715181@@tmp_rte_pmd_crypto_scheduler@sta/crypto_scheduler_scheduler_pmd.c.o'.
[1091/1656] Compiling C object 'drivers/a715181@@tmp_rte_pmd_crypto_scheduler@sta/crypto_scheduler_scheduler_pmd_ops.c.o'.
[1092/1656] Compiling C object 'drivers/a715181@@tmp_rte_pmd_octeontx_crypto@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
ninja: build stopped: subcommand failed
DPDK STV team
reply other threads:[~2019-08-08 9:23 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='ee68f5$7mlk1g@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).