From: sys_stv@intel.com
To: test-report@dpdk.org, thomas@monjalon.net
Cc: dpdk_sw_eng@intel.com, npg.sw.core.tools.prc@intel.com
Subject: [dpdk-test-report] |FAILURE| dpdk daily Intel builds
Date: 03 Nov 2020 14:07:16 -0800 [thread overview]
Message-ID: <569c58$g1m96u@orsmga005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 8210 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
_Compilation issues_
commit 62e12c18aa12e288d95cc39fcf8ba7a4fd04f2b6
Author: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Date: Fri Oct 30 21:42:16 2020 +0300
eal/windows: fix deadlock when setting alarm
DPDK git Repo: dpdk
Meson Build Summary: 24 Builds Done, 23 Successful, 1 Failures, 0 Blocked
+----------------+------------+--------------+------------+------------+-----------+----------+
| os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document |
+----------------+------------+--------------+------------+------------+-----------+----------+
| CENTOS82-64 | pass | pass | pass | pass | pass | |
| RHEL82-64 | pass | | | | | |
| UB1804-64 | pass | | | | | |
| FC33-64 | pass | pass | | | | |
| UB2010-64 | pass | | | | | |
| UB2004-64 | pass | pass | pass | | | pass |
| WIN10-64 | | pass | | | | |
| UB2004-32 | FAIL | | | | | |
| FreeBSD1201-64 | pass | pass | | pass | pass | |
| SUSE15-64 | pass | pass | | | | |
| UB2004-64N | pass | | | pass | | |
+----------------+------------+--------------+------------+------------+-----------+----------+
Test environment and configuration as below:
OS: CENTOS82-64
Kernel Version: 4.18.0-193.14.2.el8_2.x86_64
CPU info: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
GCC Version: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
Clang Version: 9.0.1 (Red Hat 9.0.1-2.module_el8.2.0+309+0c7b6b03)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-icc
x86_64-native-linuxapp-gcc+shared
x86_64-native-linuxapp-gcc+debug
OS: RHEL82-64
Kernel Version: 4.18.0-193.el8.x86_64
CPU info: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
GCC Version: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
Clang Version: 8.0.1 (Red Hat 8.0.1-1.module_el8.1.0+215+a01033fb)
x86_64-native-linuxapp-gcc
OS: UB1804-64
Kernel Version: 5.3.0-59-generic
CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: gcc (Ubuntu 8.4.0-1ubuntu1~18.04) 8.4.0
Clang Version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
x86_64-native-linuxapp-gcc
OS: FC33-64
Kernel Version: 5.8.16-300.fc33.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 10.2.1 20201005 (Red Hat 10.2.1-5)
Clang Version: 11.0.0 (Fedora 11.0.0-1.fc33)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: UB2010-64
Kernel Version: 5.8.0-25-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0
Clang Version: 11.0.0-2
x86_64-native-linuxapp-gcc
OS: UB2004-64
Kernel Version: 5.4.0-47-generic
CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: gcc (Ubuntu 10-20200416-0ubuntu1) 10.0.1 20200416 (experimental) [master revision 3c3f12e2a76:dcee354ce56:44b326839d864fc10c459916abcc97f35a9ac3de]
Clang Version: 10.0.0-4ubuntu1
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-icc
x86_64-native-linuxapp-doc
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: UB2004-32
Kernel Version: 5.4.0-47-generic
CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
Clang Version: 10.0.0-4ubuntu1
i686-native-linuxapp-gcc
OS: FreeBSD1201-64
Kernel Version: 12.1-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.74-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 9.2.0
Clang Version: 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
x86_64-native-bsdapp-gcc
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-gcc+debug
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-clang
x86_64-native-linuxapp-gcc
OS: UB2004-64N
Kernel Version: 5.8.0-050800-generic
CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
Clang Version: 10.0.0-4ubuntu1
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc+shared
*Build Failed #1:
OS: UB2004-32
Target: i686-native-linuxapp-gcc
FAILED: drivers/libtmp_rte_raw_ioat.a.p/raw_ioat_idxd_pci.c.o
gcc -Idrivers/libtmp_rte_raw_ioat.a.p -Idrivers -I../drivers -Idrivers/raw/ioat -I../drivers/raw/ioat -Ilib/librte_rawdev -I../lib/librte_rawdev -I. -I.. -Iconfig -I../config -Ilib/librte_eal/include -I../lib/librte_eal/include -Ilib/librte_eal/linux/include -I../lib/librte_eal/linux/include -Ilib/librte_eal/x86/include -I../lib/librte_eal/x86/include -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_metrics -I../lib/librte_metrics -Ilib/librte_telemetry -I../lib/librte_telemetry -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/librte_pci -I../lib/librte_pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include rte_config.h -Wextra -Wcast-qual -Wdeprecated -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-pointer-to-int-cast -D_GNU_SOURCE -m32 -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -MD -MQ drivers/libtmp_rte_raw_ioat.a.p/raw_ioat_idxd_pci.c.o -MF drivers/libtmp_rte_raw_ioat.a.p/raw_ioat_idxd_pci.c.o.d -o drivers/libtmp_rte_raw_ioat.a.p/raw_ioat_idxd_pci.c.o -c ../drivers/raw/ioat/idxd_pci.c
In file included from ../lib/librte_eal/include/rte_log.h:26,
from ../lib/librte_eal/include/rte_debug.h:17,
from ../drivers/bus/pci/rte_bus_pci.h:27,
from ../drivers/raw/ioat/idxd_pci.c:5:
../drivers/raw/ioat/idxd_pci.c: In function ‘idxd_get_wq_cfg’:
../lib/librte_eal/include/rte_common.h:248:30: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
248 | #define RTE_PTR_ADD(ptr, x) ((void*)((uintptr_t)(ptr) + (x)))
| ^
../drivers/raw/ioat/idxd_pci.c:50:9: note: in expansion of macro ‘RTE_PTR_ADD’
50 | return RTE_PTR_ADD(pci->wq_regs_base,
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
[1565/2401] Generating rte_raw_dpaa2_cmdif.sym_chk with a meson_exe.py custom command
[1566/2401] Linking static target drivers/librte_net_octeontx2.a
[1567/2401] Generating rte_raw_ntb_def with a custom command
[1568/2401] Compiling C object drivers/libtmp_rte_raw_ntb.a.p/raw_ntb_ntb_hw_intel.c.o
[1569/2401] Compiling C object drivers/libtmp_rte_net_virtio.a.p/net_virtio_virtio_rxtx.c.o
[1570/2401] Compiling C object drivers/libtmp_rte_net_vmxnet3.a.p/net_vmxnet3_vmxnet3_rxtx.c.o
[1571/2401] Compiling C object drivers/libtmp_rte_raw_ioat.a.p/raw_ioat_ioat_rawdev_test.c.o
[1572/2401] Compiling C object drivers/libtmp_rte_raw_dpaa2_qdma.a.p/raw_dpaa2_qdma_dpaa2_qdma.c.o
[1573/2401] Compiling C object drivers/libtmp_rte_raw_ntb.a.p/raw_ntb_ntb.c.o
ninja: build stopped: subcommand failed
DPDK STV team
next reply other threads:[~2020-11-03 22:07 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 22:07 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-19 21:15 sys_stv
2023-02-07 8:15 sys_stv
2023-02-07 5:05 sys_stv
2023-01-09 5:34 sys_stv
2022-12-08 21:31 sys_stv
2022-12-06 13:02 sys_stv
2022-12-05 3:36 sys_stv
2022-10-31 5:48 sys_stv
2022-10-11 10:06 sys_stv
2022-09-29 7:48 sys_stv
2022-09-29 5:44 sys_stv
2022-09-29 3:30 sys_stv
2022-09-21 21:06 sys_stv
2022-09-20 9:05 sys_stv
2022-09-19 5:24 sys_stv
2022-09-19 2:38 sys_stv
2022-09-16 10:09 sys_stv
2022-09-15 17:01 sys_stv
2022-09-14 21:06 sys_stv
2022-09-07 8:19 sys_stv
2022-08-30 7:51 sys_stv
2022-08-24 6:11 sys_stv
2022-06-22 21:09 sys_stv
2022-06-09 9:08 sys_stv
2022-06-06 7:26 sys_stv
2022-06-06 2:06 sys_stv
2022-06-01 21:06 sys_stv
2022-06-01 1:57 sys_stv
2022-05-31 21:06 sys_stv
2022-05-30 8:26 sys_stv
2022-05-26 8:57 sys_stv
2022-05-20 5:13 sys_stv
2022-05-20 4:47 sys_stv
2022-05-18 21:07 sys_stv
2022-05-18 10:08 sys_stv
2022-05-17 21:07 sys_stv
2022-05-17 9:36 sys_stv
2022-05-17 9:15 sys_stv
2022-05-17 8:58 sys_stv
2022-05-16 21:06 sys_stv
2022-05-07 7:26 sys_stv
2022-05-06 21:06 sys_stv
2022-05-06 9:49 sys_stv
2022-05-06 9:32 sys_stv
2022-03-08 21:07 sys_stv
2022-03-08 17:16 sys_stv
2022-01-21 7:59 sys_stv
2022-01-21 7:55 sys_stv
2021-12-18 21:50 sys_stv
2021-10-22 22:14 sys_stv
2021-10-14 3:03 sys_stv
2021-08-15 22:10 sys_stv
2021-06-29 15:39 sys_stv
2021-05-27 22:08 sys_stv
2021-05-07 1:05 sys_stv
2021-03-22 22:07 sys_stv
2021-01-28 22:07 sys_stv
2021-01-27 22:07 sys_stv
2021-01-26 22:08 sys_stv
2021-01-26 6:13 sys_stv
2020-11-05 22:08 sys_stv
2020-10-20 5:41 sys_stv
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='569c58$g1m96u@orsmga005-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dpdk_sw_eng@intel.com \
--cc=npg.sw.core.tools.prc@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).