automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |FAILURE| [GIT MASTER] 1b593b0c092a0e905cb1c05ba01acb6690fb0db2
Date: Wed, 24 Jan 2024 00:08:21 -0800 (PST)	[thread overview]
Message-ID: <65b0c575.170a0220.3953a.9c78SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: dpdk-next-net

1b593b0c092a0e905cb1c05ba01acb6690fb0db2 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | FAIL               | PASS                 |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 38           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+

==== 20 line log output for Windows Server 2019 (dpdk_meson_compile): ====
[234/817] Linking target lib/rte_cryptodev-24.dll
Creating library lib\rte_cryptodev.lib and object lib\rte_cryptodev.exp
[235/817] Linking target lib/rte_gpudev-24.dll
Creating library lib\rte_gpudev.lib and object lib\rte_gpudev.exp
[236/817] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_generic_flow.c.obj
[237/817] Generating symbol file lib/rte_net-24.dll.p/rte_net-24.dll.symbols
[238/817] Compiling C object drivers/net/ixgbe/base/libixgbe_base.a.p/ixgbe_dcb_82599.c.obj
[239/817] Linking target lib/rte_ethdev-24.dll
FAILED: lib/rte_ethdev-24.dll
"clang"  -Wl,/MACHINE:X64 -Wl,/OUT:lib/rte_ethdev-24.dll lib/librte_ethdev.a.p/ethdev_ethdev_driver.c.obj lib/librte_ethdev.a.p/ethdev_ethdev_private.c.obj lib/librte_ethdev.a.p/ethdev_ethdev_profile.c.obj lib/librte_ethdev.a.p/ethdev_ethdev_trace_points.c.obj lib/librte_ethdev.a.p/ethdev_rte_class_eth.c.obj lib/librte_ethdev.a.p/ethdev_rte_ethdev.c.obj lib/librte_ethdev.a.p/ethdev_rte_ethdev_cman.c.obj lib/librte_ethdev.a.p/ethdev_rte_ethdev_telemetry.c.obj lib/librte_ethdev.a.p/ethdev_rte_flow.c.obj lib/librte_ethdev.a.p/ethdev_rte_mtr.c.obj lib/librte_ethdev.a.p/ethdev_rte_tm.c.obj lib/librte_ethdev.a.p/ethdev_sff_telemetry.c.obj lib/librte_ethdev.a.p/ethdev_sff_common.c.obj lib/librte_ethdev.a.p/ethdev_sff_8079.c.obj lib/librte_ethdev.a.p/ethdev_sff_8472.c.obj lib/librte_ethdev.a.p/ethdev_sff_8636.c.obj "-LC:\Program Files\Mellanox\MLNX_WinOF2_DevX_SDK\lib" "-Wl,/nologo" "-Wl,/release" "-Wl,/nologo" "-Wl,/OPT:REF" "-Wl,/DLL" "-Wl,/IMPLIB:lib\rte_ethdev.lib" "lib\rte_eal.lib" "lib
 \rte_log.lib" "lib\rte_kvargs.lib" "lib\rte_net.lib" "lib\rte_mbuf.lib" "lib\rte_mempool.lib" "lib\rte_ring.lib" "lib\rte_telemetry.lib" "lib\rte_meter.lib" "-Wl,/def:C:\Users\builder\jenkins\workspace\Windows-Compile-DPDK-Meson\dpdk\build\lib\rte_ethdev_exports.def" "-ldbghelp" "-lsetupapi" "-lws2_32" "-lmincore" "-lkernel32" "-luser32" "-lgdi32" "-lwinspool" "-lshell32" "-lole32" "-loleaut32" "-luuid" "-lcomdlg32" "-ladvapi32"
rte_ethdev_exports.def : error LNK2001: unresolved external symbol rte_eth_tx_queue_count
lib\rte_ethdev.lib : fatal error LNK1120: 1 unresolved externals
clang: error: linker command failed with exit code 1120 (use -v to see invocation)
[240/817] Compiling C object drivers/net/ixgbe/base/libixgbe_base.a.p/ixgbe_hv_vf.c.obj
[241/817] Generating symbol file lib/rte_cryptodev-24.dll.p/rte_cryptodev-24.dll.symbols
[242/817] Linking target lib/rte_hash-24.dll
Creating library lib\rte_hash.lib and object lib\rte_hash.exp
[243/817] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow.c.obj
[244/817] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_ixgbe_ixgbe_ipsec.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27779/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-01-24  8:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  8:08 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-24 21:59 dpdklab
2024-01-24 21:53 dpdklab
2024-01-24 21:48 dpdklab
2024-01-24 21:45 dpdklab
2024-01-24 21:44 dpdklab
2024-01-24 21:43 dpdklab
2024-01-24 21:37 dpdklab
2024-01-24 21:34 dpdklab
2024-01-24 21:34 dpdklab
2024-01-24 21:32 dpdklab
2024-01-24 21:31 dpdklab
2024-01-24 21:30 dpdklab
2024-01-24 21:25 dpdklab
2024-01-24 20:58 dpdklab
2024-01-24  8:47 dpdklab
2024-01-24  8:15 dpdklab
2024-01-24  8:14 dpdklab
2024-01-24  8:07 dpdklab
2024-01-24  8:06 dpdklab
2024-01-24  7:55 dpdklab
2024-01-24  7:55 dpdklab
2024-01-24  7:54 dpdklab
2024-01-24  7:53 dpdklab
2024-01-24  7:53 dpdklab
2024-01-24  7:52 dpdklab
2024-01-24  7:51 dpdklab
2024-01-24  7:46 dpdklab

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=65b0c575.170a0220.3953a.9c78SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.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).