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-next-virtio daily Intel builds
Date: 23 Nov 2022 15:54:14 -0800 [thread overview]
Message-ID: <8483a8$su1q8i@fmsmga005-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7428 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
_Compilation issues_
commit ece9b85149e377429e9691bde02c55fa48ac938a
Author: Taekyung Kim <kim.tae.kyung@navercorp.com>
Date: Thu Nov 10 13:09:43 2022 +0900
vdpa/ifc: fix error handling of updating data path
DPDK git Repo: dpdk-next-virtio
Meson Build Summary: 29 Builds Done, 28 Successful, 1 Failures, 0 Blocked
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| FC36-64 | pass | pass | | | | | |
| FreeBSD13-64 | pass | pass | | pass | pass | | |
| RHEL86-64 | pass | pass | | pass | pass | | |
| SUSE15-64 | pass | pass | | | | | |
| RHEL90-64 | pass | | | | | | |
| UB2004-64 | pass | pass | | | | pass | |
| UB2204-32 | pass | | | | | | |
| UB2204-64N | pass | | | pass | | | |
| UB2204-64 | pass | pass | | | | pass | pass |
| CentOS79-64 | pass | | | | | | |
| RHEL86-64Rt | pass | pass | | | | | |
| UB2210-64 | pass | | | | | | |
| FC37-64 | pass | fail | | | | | |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
Comments:
Because of DPDK bug (https://bugs.dpdk.org/show_bug.cgi?id=928),
All the dpdk-next-* branch add `Ddisable_drivers=event/cnxk` option when build with ICC complier.
Test environment and configuration as below:
OS: FC36-64
Kernel Version: 5.17.7-300.fc36.x86_64
GCC Version: gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1)
Clang Version: 14.0.0 (Fedora 14.0.0-1.fc36)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: FreeBSD13-64
Kernel Version: 13.1-RELEASE
GCC Version: gcc (FreeBSD Ports Collection) 10.3.0
Clang Version: 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
x86_64-native-bsdapp-gcc
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-gcc+debug
OS: RHEL86-64
Kernel Version: 4.18.0-372.9.1.el8.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-13)
Clang Version: 14.0.0 (Red Hat 14.0.0-1.module_el8.7.0+1142+5343df54)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc+shared
x86_64-native-linuxapp-gcc+debug
OS: SUSE15-64
Kernel Version: 5.14.21-150400.22-default
GCC Version: gcc (SUSE Linux) 7.5.0
Clang Version: 11.0.1
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
OS: RHEL90-64
Kernel Version: 5.14.0-70.13.1.el9_0.x86_64
GCC Version: gcc (GCC) 11.2.1 20220127 (Red Hat 11.2.1-9)
Clang Version: 13.0.1 (Red Hat 13.0.1-1.el9)
x86_64-native-linuxapp-gcc
OS: UB2004-64
Kernel Version: 5.8.0-48-generic
GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
Clang Version: 10.0.0-4ubuntu1
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-doc
OS: UB2204-32
Kernel Version: 5.15.0-25-generic
GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
Clang Version: NA
i686-native-linuxapp-gcc
OS: UB2204-64N
Kernel Version: 5.17.5-051705-generic
GCC Version: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang Version: 14.0.0-1ubuntu1
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc+shared
OS: UB2204-64
Kernel Version: 5.15.0-25-generic
GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
Clang Version: 14.0.0-1ubuntu1
x86_64-native-linuxapp-gcc+16byte
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-doc
OS: CentOS79-64
Kernel Version: 3.10.0-1160.el7.x86_64
GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-gcc
OS: RHEL86-64Rt
Kernel Version: 4.18.0-372.9.1.rt7.166.el8.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-13)
Clang Version: 14.0.0 (Red Hat 14.0.0-1.module_el8.7.0+1142+5343df54)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: UB2210-64
Kernel Version: 5.19.0-21-generic
GCC Version: gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0
Clang Version: 15.0.2-1
x86_64-native-linuxapp-gcc
OS: FC37-64
Kernel Version: 6.0.7-301.fc37.x86_64
GCC Version: gcc (GCC) 12.2.1 20220819 (Red Hat 12.2.1-2)
Clang Version: 15.0.4 (Fedora 15.0.4-1.fc37)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
*Build Failed #1:
OS: FC37-64
Target: x86_64-native-linuxapp-clang
FAILED: lib/librte_eal.a.p/eal_common_rte_service.c.o
clang -Ilib/librte_eal.a.p -Ilib -I../lib -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -fcolor-diagnostics -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -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-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API '-DABI_VERSION="23.0"' -DRTE_LIBEAL_USE_GETENTROPY -DRTE_LOG_DEFAULT_LOGTYPE=lib.eal -MD -MQ lib/librte_eal.a.p/eal_common_rte_service.c.o -MF lib/librte_eal.a.p/eal_common_rte_service.c.o.d -o lib/librte_eal.a.p/eal_common_rte_service.c.o -c ../lib/eal/common/rte_service.c
../lib/eal/common/rte_service.c:110:6: error: variable 'count' set but not used [-Werror,-Wunused-but-set-variable]
int count = 0;
^
1 error generated.
[38/3622] Linking target lib/librte_kvargs.so.23.0
[39/3622] Compiling C object lib/librte_eal.a.p/eal_common_malloc_elem.c.o
[40/3622] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_cpuflags.c.o
[41/3622] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_dynmem.c.o
[42/3622] Compiling C object lib/librte_eal.a.p/eal_common_malloc_heap.c.o
[43/3622] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_options.c.o
[44/3622] Compiling C object lib/librte_eal.a.p/eal_common_rte_malloc.c.o
[45/3622] Compiling C object lib/librte_eal.a.p/eal_common_rte_random.c.o
[46/3622] Generating lib/telemetry.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped
DPDK STV team
next reply other threads:[~2022-11-23 23:54 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 23:54 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-21 23:52 sys_stv
2023-05-20 23:52 sys_stv
2023-05-20 0:06 sys_stv
2023-05-19 0:19 sys_stv
2023-05-18 1:47 sys_stv
2023-05-17 0:08 sys_stv
2023-05-15 23:53 sys_stv
2023-01-09 23:35 sys_stv
2023-01-09 8:21 sys_stv
2022-11-29 0:04 sys_stv
2022-11-28 11:29 sys_stv
2022-11-23 8:12 sys_stv
2022-10-31 4:54 sys_stv
2022-10-13 23:16 sys_stv
2022-09-20 23:29 sys_stv
2022-09-19 7:00 sys_stv
2022-09-19 4:14 sys_stv
2022-09-12 22:44 sys_stv
2022-09-11 23:00 sys_stv
2022-09-09 2:55 sys_stv
2022-09-08 22:53 sys_stv
2022-09-07 14:05 sys_stv
2022-09-07 9:57 sys_stv
2022-09-06 22:43 sys_stv
2022-08-29 7:27 sys_stv
2022-08-25 22:49 sys_stv
2022-06-27 6:06 sys_stv
2022-06-26 22:34 sys_stv
2022-06-25 22:33 sys_stv
2022-06-24 22:33 sys_stv
2022-06-06 22:39 sys_stv
2022-06-01 22:32 sys_stv
2022-06-01 4:53 sys_stv
2022-05-31 22:32 sys_stv
2022-05-31 16:53 sys_stv
2022-05-31 10:53 sys_stv
2022-05-31 4:53 sys_stv
2022-05-30 22:39 sys_stv
2022-05-18 22:35 sys_stv
2022-05-17 22:35 sys_stv
2022-05-17 16:54 sys_stv
2022-05-17 11:06 sys_stv
2022-05-16 22:46 sys_stv
2022-05-07 4:56 sys_stv
2022-05-06 22:46 sys_stv
2022-02-15 8:03 sys_stv
2022-01-28 11:04 sys_stv
2022-01-28 9:42 sys_stv
2022-01-28 5:04 sys_stv
2022-01-27 23:04 sys_stv
2022-01-27 17:04 sys_stv
2022-01-27 11:05 sys_stv
2022-01-27 8:15 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='8483a8$su1q8i@fmsmga005-auth.fm.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).