automatic DPDK test reports
 help / color / mirror / Atom feed
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-net-mlx daily Intel builds
Date: 30 Oct 2022 21:06:47 -0700	[thread overview]
Message-ID: <15ae1a$m0ijft@fmsmga002-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 11505 bytes --]


Test-Label: Intel-compilation
Test-Status: FAILURE
_Compilation issues_


commit e0ba4a36c6554abe14bc64be7e35fc02d3792f3d
Author: Tal Shnaiderman <talshn@nvidia.com>
Date:   Wed Oct 12 09:49:49 2022 +0300

    net/mlx5: fix thread termination check on Windows

DPDK git Repo: dpdk-next-net-mlx 


Meson Build Summary: 27 Builds Done, 25 Successful, 2 Failures, 0 Blocked

+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| os           | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| FC36-64      | pass       | pass         |            |            |           |          |            |
| FreeBSD13-64 | fail       | pass         |            | pass       | fail      |          |            |
| 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       |              |            |            |           |          |            |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+

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.2.0-19ubuntu1) 11.2.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



*Build Failed #1:
OS: FreeBSD13-64
Target: x86_64-native-bsdapp-gcc
FAILED: drivers/librte_crypto_ipsec_mb.so.23.0 
gcc  -o drivers/librte_crypto_ipsec_mb.so.23.0 drivers/librte_crypto_ipsec_mb.so.23.0.p/meson-generated_.._rte_crypto_ipsec_mb.pmd.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_private.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_ops.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_mb.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_gcm.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_chacha_poly.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_kasumi.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_snow3g.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_zuc.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,librte_crypto_ipsec_mb.so.23 -Wl,--no-as-needed -pthread -lm -lexecinfo '-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/' -Wl,-rpath-link,/root/FreeBSD13-64_K13_GCC10.3.0/x86_64-native-bsdapp-gcc/20221031113238/dpdk/x86_64-native-bsdapp-gcc/lib -Wl,-rpath-link,/root/FreeBSD13-64_K13_GCC10.3.0/x86_64-native-bsdapp-gcc/20221031113238/dpdk/x86_64-native-bsdapp-gcc/drivers lib/librte_cryptodev.so.23.0 lib/librte_eal.so.23.0 lib/librte_kvargs.so.23.0 lib/librte_telemetry.so.23.0 lib/librte_mbuf.so.23.0 lib/librte_mempool.so.23.0 lib/librte_ring.so.23.0 lib/librte_rcu.so.23.0 drivers/librte_bus_vdev.so.23.0 lib/librte_net.so.23.0 lib/librte_security.so.23.0 -Wl,--version-script=/root/FreeBSD13-64_K13_GCC10.3.0/x86_64-native-bsdapp-gcc/20221031113238/dpdk/drivers/crypto/ipsec_mb/version.map -lIPSec_MB -Wl,--end-group
/usr/local/bin/ld: drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_ops.c.o: in function `ipsec_mb_qp_setup':
ipsec_mb_ops.c:(.text+0x30d): undefined reference to `imb_set_pointers_mb_mgr'
/usr/local/bin/ld: ipsec_mb_ops.c:(.text+0x452): undefined reference to `imb_set_pointers_mb_mgr'
/usr/local/bin/ld: ipsec_mb_ops.c:(.text+0x4ec): undefined reference to `imb_get_mb_mgr_size'
collect2: error: ld returned 1 exit status
[1566/2064] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_multicore.c.o
[1567/2064] Compiling C object drivers/libtmp_rte_event_skeleton.a.p/event_skeleton_skeleton_eventdev.c.o
[1568/2064] Generating rte_crypto_virtio.sym_chk with a custom command (wrapped by meson to capture output)
[1569/2064] Compiling C object drivers/libtmp_rte_event_opdl.a.p/event_opdl_opdl_test.c.o
[1570/2064] Compiling C object drivers/libtmp_rte_event_dsw.a.p/event_dsw_dsw_event.c.o
[1571/2064] Compiling C object drivers/libtmp_rte_event_sw.a.p/event_sw_sw_evdev_worker.c.o
[1572/2064] Compiling C object drivers/libtmp_rte_event_opdl.a.p/event_opdl_opdl_ring.c.o
[1573/2064] Compiling C object drivers/libtmp_rte_event_sw.a.p/event_sw_sw_evdev_scheduler.c.o
[1574/2064] Compiling C object drivers/libtmp_rte_event_sw.a.p/event_sw_sw_evdev_selftest.c.o
ninja: build stopped




*Build Failed #2:
OS: FreeBSD13-64
Target: x86_64-native-bsdapp-gcc+debug
FAILED: drivers/librte_crypto_ipsec_mb.so.23.0 
gcc  -o drivers/librte_crypto_ipsec_mb.so.23.0 drivers/librte_crypto_ipsec_mb.so.23.0.p/meson-generated_.._rte_crypto_ipsec_mb.pmd.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_private.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_ops.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_mb.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_gcm.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_chacha_poly.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_kasumi.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_snow3g.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_zuc.c.o -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,librte_crypto_ipsec_mb.so.23 -Wl,--no-as-needed -pthread -lm -lexecinfo '-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/' -Wl,-rpath-link,/root/FreeBSD13-64_K13_GCC10.3.0/x86_64-native-bsdapp-gcc+debug/20221031113238/dpdk/x86_64-native-bsdapp-gcc+debug/lib -Wl,-rpath-link,/root/FreeBSD13-64_K13_GCC10.3.0/x86_64-native-bsdapp-gcc+debug/20221031113238/dpdk/x86_64-native-bsdapp-gcc+debug/drivers lib/librte_cryptodev.so.23.0 lib/librte_eal.so.23.0 lib/librte_kvargs.so.23.0 lib/librte_telemetry.so.23.0 lib/librte_mbuf.so.23.0 lib/librte_mempool.so.23.0 lib/librte_ring.so.23.0 lib/librte_rcu.so.23.0 drivers/librte_bus_vdev.so.23.0 lib/librte_net.so.23.0 lib/librte_security.so.23.0 -Wl,--version-script=/root/FreeBSD13-64_K13_GCC10.3.0/x86_64-native-bsdapp-gcc+debug/20221031113238/dpdk/drivers/crypto/ipsec_mb/version.map -lIPSec_MB -Wl,--end-group
/usr/local/bin/ld: drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_ops.c.o: in function `ipsec_mb_alloc_mgr_from_memzone':
/root/FreeBSD13-64_K13_GCC10.3.0/x86_64-native-bsdapp-gcc+debug/20221031113238/dpdk/x86_64-native-bsdapp-gcc+debug/../drivers/crypto/ipsec_mb/ipsec_mb_ops.c:197: undefined reference to `imb_set_pointers_mb_mgr'
/usr/local/bin/ld: /root/FreeBSD13-64_K13_GCC10.3.0/x86_64-native-bsdapp-gcc+debug/20221031113238/dpdk/x86_64-native-bsdapp-gcc+debug/../drivers/crypto/ipsec_mb/ipsec_mb_ops.c:187: undefined reference to `imb_set_pointers_mb_mgr'
/usr/local/bin/ld: /root/FreeBSD13-64_K13_GCC10.3.0/x86_64-native-bsdapp-gcc+debug/20221031113238/dpdk/x86_64-native-bsdapp-gcc+debug/../drivers/crypto/ipsec_mb/ipsec_mb_ops.c:178: undefined reference to `imb_get_mb_mgr_size'
collect2: error: ld returned 1 exit status
[1566/2064] Compiling C object drivers/libtmp_rte_event_opdl.a.p/event_opdl_opdl_evdev_init.c.o
[1567/2064] Compiling C object drivers/libtmp_rte_event_opdl.a.p/event_opdl_opdl_evdev_xstats.c.o
[1568/2064] Generating drivers/rte_crypto_scheduler.pmd.c with a custom command
[1569/2064] Generating drivers/rte_crypto_virtio.sym_chk with a custom command (wrapped by meson to capture output)
[1570/2064] Compiling C object drivers/libtmp_rte_event_skeleton.a.p/event_skeleton_skeleton_eventdev.c.o
[1571/2064] Compiling C object drivers/libtmp_rte_event_opdl.a.p/event_opdl_opdl_test.c.o
[1572/2064] Compiling C object drivers/libtmp_rte_event_dsw.a.p/event_dsw_dsw_event.c.o
[1573/2064] Compiling C object drivers/libtmp_rte_event_opdl.a.p/event_opdl_opdl_ring.c.o
[1574/2064] Compiling C object drivers/libtmp_rte_event_sw.a.p/event_sw_sw_evdev_scheduler.c.o
ninja: build stopped


DPDK STV team

             reply	other threads:[~2022-10-31  4:06 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  4:06 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-10 23:13 sys_stv
2023-06-09 23:34 sys_stv
2023-06-09  3:11 sys_stv
2023-06-08 23:48 sys_stv
2023-05-24  7:21 sys_stv
2023-05-24  4:15 sys_stv
2023-05-23  8:14 sys_stv
2023-05-22 23:26 sys_stv
2023-05-21 23:16 sys_stv
2023-05-20 23:16 sys_stv
2023-05-19 23:30 sys_stv
2023-05-18 23:43 sys_stv
2023-05-18  0:42 sys_stv
2023-05-16 23:33 sys_stv
2023-05-15 23:17 sys_stv
2023-01-09 22:59 sys_stv
2022-11-20 22:51 sys_stv
2022-10-13 22:43 sys_stv
2022-09-12 22:20 sys_stv
2022-09-02 22:20 sys_stv
2022-06-29  1:40 sys_stv
2022-06-27 22:21 sys_stv
2022-06-26 22:13 sys_stv
2022-06-25 22:12 sys_stv
2022-06-24 22:12 sys_stv
2022-06-07  2:32 sys_stv
2022-06-06 22:10 sys_stv
2022-06-01 22:54 sys_stv
2022-06-01 22:10 sys_stv
2022-06-01  5:04 sys_stv
2022-06-01  3:01 sys_stv
2022-05-31 22:53 sys_stv
2022-05-31 22:10 sys_stv
2022-05-31 17:04 sys_stv
2022-05-31 11:04 sys_stv
2022-05-31  5:04 sys_stv
2022-05-30 22:10 sys_stv
2022-05-18 22:56 sys_stv
2022-05-18 22:13 sys_stv
2022-05-17 22:57 sys_stv
2022-05-17 22:13 sys_stv
2022-05-17 17:05 sys_stv
2022-05-17 10:44 sys_stv
2022-05-16 23:09 sys_stv
2022-05-16 22:24 sys_stv
2022-05-07  5:08 sys_stv
2022-05-06 23:10 sys_stv
2022-05-06 22:21 sys_stv
2022-01-28 11:15 sys_stv
2022-01-28  9:53 sys_stv
2022-01-27 23:15 sys_stv
2022-01-27 17:15 sys_stv
2022-01-27 11:16 sys_stv
2022-01-27  8:04 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='15ae1a$m0ijft@fmsmga002-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).