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-eventdev daily Intel builds
Date: 15 May 2023 15:06:55 -0700 [thread overview]
Message-ID: <374626$k74ofb@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 9033 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
_Compilation issues_
commit 19620da5ca6662f129cf4d102598313ea3800272
Author: Pavan Nikhilesh <pbhagavatula@marvell.com>
Date: Fri Apr 7 13:44:10 2023 +0530
doc: fix event timer adapter guide
DPDK git Repo: dpdk-next-eventdev
Meson Build Summary: 27 Builds Done, 26 Successful, 1 Failures, 0 Blocked
+-------------------+------------+--------------+------------+------------+-----------+----------+------------+
| os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+-------------------+------------+--------------+------------+------------+-----------+----------+------------+
| OpenAnolis8.8-64 | pass | | | | | | |
| FreeBSD13-64 | pass | pass | | pass | pass | | |
| RHEL92-64 | pass | pass | | pass | pass | | |
| SUSE15-64 | pass | pass | | | | | |
| CBL-Mariner2.0-64 | pass | | | | | | |
| UB2004-64 | pass | | | | | | |
| UB2204-32 | pass | | | | | | |
| RHEL87-64 | pass | | | | | | |
| UB2204-64N | pass | | | pass | | | |
| UB2204-64 | pass | pass | | | | pass | pass |
| CentOS79-64 | pass | | | | | | |
| RHEL92-64Rt | pass | | | | | | |
| UB2304-64 | pass | | | | | | |
| FC38-64 | fail | pass | | | | | |
| UB2204-64Rt | pass | | | | | | |
+-------------------+------------+--------------+------------+------------+-----------+----------+------------+
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: OpenAnolis8.8-64
Kernel Version: 5.10.134-13.an8.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Anolis 8.5.0-10.0.3)
Clang Version: 13.0.1 (Anolis 13.0.1-2.0.2.module+an8.7.0+10996+1588f068)
x86_64-native-linuxapp-gcc
OS: FreeBSD13-64
Kernel Version: 13.2-RELEASE
GCC Version: gcc (FreeBSD Ports Collection) 12.2.0
Clang Version: 14.0.5 (https://github.com/llvm/llvm-project.git llvmorg-14.0.5-0-gc12386ae247c)
x86_64-native-bsdapp-gcc
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-gcc+debug
OS: RHEL92-64
Kernel Version: 5.14.0-284.11.1.el9_2.x86_64
GCC Version: gcc (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4)
Clang Version: 15.0.7 (Red Hat 15.0.7-2.el9)
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: CBL-Mariner2.0-64
Kernel Version: 5.15.55.1_2e9a4f9+
GCC Version: gcc (GCC) 11.2.0
Clang Version: NA
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-gcc
OS: UB2204-32
Kernel Version: 5.15.0-58-generic
GCC Version: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang Version: NA
i686-native-linuxapp-gcc
OS: RHEL87-64
Kernel Version: 4.18.0-425.3.1.el8.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-15)
Clang Version: NA
x86_64-native-linuxapp-gcc
OS: UB2204-64N
Kernel Version: 6.2.13-060213-generic
GCC Version: gcc (Ubuntu 12.1.0-2ubuntu1~22.04) 12.1.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-58-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+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.81.1.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: RHEL92-64Rt
Kernel Version: 5.14.0-284.11.1.rt14.296.el9_2.x86_64
GCC Version: gcc (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4)
Clang Version: 15.0.7 (Red Hat 15.0.7-2.el9)
x86_64-native-linuxapp-gcc
OS: UB2304-64
Kernel Version: 6.2.0-20-generic
GCC Version: gcc (Ubuntu 12.2.0-17ubuntu1) 12.2.0
Clang Version: NA
x86_64-native-linuxapp-gcc
OS: FC38-64
Kernel Version: 6.2.9-300.fc38.x86_64
GCC Version: gcc (GCC) 13.0.1 20230401 (Red Hat 13.0.1-0)
Clang Version: 16.0.0 (Fedora 16.0.0-2.fc38)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: UB2204-64Rt
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
*Build Failed #1:
OS: FC38-64
Target: x86_64-native-linuxapp-gcc
FAILED: examples/dpdk-ip_pipeline.p/ip_pipeline_thread.c.o
gcc -Iexamples/dpdk-ip_pipeline.p -Iexamples -I../examples -Iexamples/ip_pipeline -I../examples/ip_pipeline -I../examples/common -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 -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/ethdev -I../lib/ethdev -Ilib/meter -I../lib/meter -Ilib/cmdline -I../lib/cmdline -Ilib/pipeline -I../lib/pipeline -Ilib/port -I../lib/port -Ilib/sched -I../lib/sched -Ilib/ip_frag -I../lib/ip_frag -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Ilib/cryptodev -I../lib/cryptodev -Ilib/eventdev -I../lib/eventdev -Ilib/timer -I../lib/timer -Ilib/table -I../lib/table -Ilib/lpm -I../lib/lpm -Ilib/acl -I../lib/acl -Ilib/ipsec -I../lib/ipsec -Ilib/security -I../lib/security -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -fdiagnostics-color=always -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-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -march=native -Wno-format-truncation -DALLOW_EXPERIMENTAL_API -MD -MQ examples/dpdk-ip_pipeline.p/ip_pipeline_thread.c.o -MF examples/dpdk-ip_pipeline.p/ip_pipeline_thread.c.o.d -o examples/dpdk-ip_pipeline.p/ip_pipeline_thread.c.o -c ../examples/ip_pipeline/thread.c
In function ‘thread_msg_handle’,
inlined from ‘thread_main’ at ../examples/ip_pipeline/thread.c:3130:6:
../examples/ip_pipeline/thread.c:535:20: error: ‘req’ may be used uninitialized [-Werror=maybe-uninitialized]
535 | if (req == NULL)
| ^
../examples/ip_pipeline/thread.c: In function ‘thread_main’:
../examples/ip_pipeline/thread.c:433:32: note: ‘req’ was declared here
433 | struct thread_msg_req *req;
| ^~~
cc1: all warnings being treated as errors
[3350/3478] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_event_helper.c.o
[3351/3478] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_ipsec.c.o
[3352/3478] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_ipsec_process.c.o
[3353/3478] Linking target app/test/dpdk-test
[3354/3478] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_parser.c.o
[3355/3478] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_rt.c.o
[3356/3478] Linking target examples/dpdk-ip_reassembly
[3357/3478] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_ipsec_worker.c.o
[3358/3478] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_ipsec-secgw.c.o
ninja: build stopped
DPDK STV team
next reply other threads:[~2023-05-15 22:07 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 22:06 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-26 11:28 sys_stv
2023-02-08 7:30 sys_stv
2023-01-09 21:48 sys_stv
2022-11-23 21:51 sys_stv
2022-11-23 6:17 sys_stv
2022-11-22 8:51 sys_stv
2022-10-13 21:40 sys_stv
2022-10-11 21:53 sys_stv
2022-10-07 3:47 sys_stv
2022-09-20 6:29 sys_stv
2022-09-19 3:02 sys_stv
2022-09-15 7:15 sys_stv
2022-09-14 13:13 sys_stv
2022-09-14 3:58 sys_stv
2022-09-13 16:43 sys_stv
2022-09-09 21:30 sys_stv
2022-09-01 21:31 sys_stv
2022-06-26 21:28 sys_stv
2022-06-25 21:28 sys_stv
2022-06-24 21:28 sys_stv
2022-06-06 21:28 sys_stv
2022-06-06 16:57 sys_stv
2022-06-01 23:15 sys_stv
2022-06-01 21:28 sys_stv
2022-06-01 2:18 sys_stv
2022-05-31 23:21 sys_stv
2022-05-31 21:27 sys_stv
2022-05-31 17:25 sys_stv
2022-05-31 11:26 sys_stv
2022-05-31 5:26 sys_stv
2022-05-30 21:28 sys_stv
2022-05-18 23:28 sys_stv
2022-05-18 21:29 sys_stv
2022-05-17 23:30 sys_stv
2022-05-17 21:29 sys_stv
2022-05-17 17:39 sys_stv
2022-05-17 11:39 sys_stv
2022-05-17 9:58 sys_stv
2022-05-16 23:43 sys_stv
2022-05-16 21:38 sys_stv
2022-05-07 5:46 sys_stv
2022-05-06 23:48 sys_stv
2022-05-06 21:31 sys_stv
2022-03-29 21:50 sys_stv
2022-03-12 21:40 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='374626$k74ofb@orsmga006-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).