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, liwencheng <liwencheng@phytium.com.cn>
Subject: |FAILURE| pw148008-148010 [PATCH] [v2,3/3] usertools/dpdk-devbind: a
Date: Tue, 05 Nov 2024 23:54:01 -0800 (PST)	[thread overview]
Message-ID: <672b2099.050a0220.c9ab3.3d62SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1730864040-1309652-1-git-send-email-liwencheng@phytium.com.cn>

Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/148010

_Testing issues_

Submitter: liwencheng <liwencheng@phytium.com.cn>
Date: Wednesday, November 06 2024 03:34:00 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:64f27886b8bf127cd365a8a3ed5c05852a5ae81d

148008-148010 --> testing issues

Upstream job id: Generic-DPDK-Compile-Meson#330119

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| RHEL9 (ARM)                            | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK                   | PASS               |
+----------------------------------------+--------------------+
| Fedora 39 (ARM Clang)                  | FAIL               |
+----------------------------------------+--------------------+
| Fedora 39 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Fedora 40 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Fedora 40 (ARM Clang)                  | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+

==== 20 line log output for Ubuntu 20.04 aarch32 GCC Cross Compile (dpdk_meson_compile): ====
[1356/2309] Compiling C object drivers/librte_net_ixgbe.so.25.0.p/meson-generated_.._rte_net_ixgbe.pmd.c.o
[1357/2309] Linking target drivers/librte_net_ixgbe.so.25.0
[1358/2309] Generating symbol file drivers/librte_net_ixgbe.so.25.0.p/librte_net_ixgbe.so.25.0.symbols
[1359/2309] Compiling C object drivers/net/macb/base/libmacb_base.a.p/macb_common.c.o
[1360/2309] Compiling C object drivers/net/macb/base/libmacb_base.a.p/macb_uio.c.o
[1361/2309] Compiling C object drivers/net/macb/base/libmacb_base.a.p/generic_phy.c.o
[1362/2309] Linking static target drivers/net/macb/base/libmacb_base.a
[1363/2309] Compiling C object drivers/libtmp_rte_net_macb.a.p/net_macb_macb_ethdev.c.o
[1364/2309] Compiling C object drivers/libtmp_rte_net_macb.a.p/net_macb_macb_rxtx.c.o
[1365/2309] Compiling C object drivers/libtmp_rte_net_macb.a.p/net_macb_macb_rxtx_vec_neon.c.o
FAILED: drivers/libtmp_rte_net_macb.a.p/net_macb_macb_rxtx_vec_neon.c.o
ccache arm-linux-gnueabihf-gcc -Idrivers/libtmp_rte_net_macb.a.p -Idrivers -I../drivers -Idrivers/net/macb -I../drivers/net/macb -Idrivers/net/macb/base -I../drivers/net/macb/base -Ilib/ethdev -I../lib/ethdev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/arm/include -I../lib/eal/arm/include -I../kernel/linux -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wfo
 rmat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-pointer-to-int-cast -D_GNU_SOURCE -fPIC -march=armv8-a+simd -mfpu=auto -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-address-of-packed-member -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.macb -MD -MQ drivers/libtmp_rte_net_macb.a.p/net_macb_macb_rxtx_vec_neon.c.o -MF drivers/libtmp_rte_net_macb.a.p/net_macb_macb_rxtx_vec_neon.c.o.d -o drivers/libtmp_rte_net_macb.a.p/net_macb_macb_rxtx_vec_neon.c.o -c ../drivers/net/macb/macb_rxtx_vec_neon.c
../drivers/net/macb/macb_rxtx_vec_neon.c: In function 'macb_xmit_pkts_vec':
../drivers/net/macb/macb_rxtx_vec_neon.c:592:7: error: implicit declaration of function 'vmaxv_u16'; did you mean 'vmaxq_u16'? [-Werror=implicit-function-declaration]
592 |   if (vmaxv_u16(nb_segs_v) > 1) {
|       ^~~~~~~~~
|       vmaxq_u16
../drivers/net/macb/macb_rxtx_vec_neon.c:592:7: error: nested extern declaration of 'vmaxv_u16' [-Werror=nested-externs]
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: Depends on container host
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Debian 12 with MUSDK
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 39 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

Fedora 40 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

Ubuntu 20.04 (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 22.04 (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 24.04 (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

CentOS Stream 9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Debian 12 (arm)
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: Depends on container host
	Compiler: clang 10.0.0-4ubuntu1

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: Depends on container host
	Compiler: gcc 9.4.0

Ubuntu 20.04 ARM SVE
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31832/

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2024-11-06  7:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1730864040-1309652-1-git-send-email-liwencheng@phytium.com.cn>
2024-11-06  3:03 ` |SUCCESS| pw148008-148010 [PATCH v2 3/3] usertools/dpdk-devbind: add bind/unbind for platform device qemudev
2024-11-06  3:08 ` qemudev
2024-11-06  3:35 ` |SUCCESS| pw148010 " checkpatch
2024-11-06  4:09 ` |PENDING| pw148008-148010 [PATCH] [v2,3/3] usertools/dpdk-devbind: a dpdklab
2024-11-06  4:13 ` dpdklab
2024-11-06  4:18 ` |FAILURE| " dpdklab
2024-11-06  4:18 ` dpdklab
2024-11-06  4:19 ` |SUCCESS| " dpdklab
2024-11-06  4:19 ` |FAILURE| " dpdklab
2024-11-06  4:21 ` dpdklab
2024-11-06  4:23 ` |SUCCESS| " dpdklab
2024-11-06  4:25 ` |PENDING| " dpdklab
2024-11-06  4:25 ` |SUCCESS| " dpdklab
2024-11-06  4:29 ` |SUCCESS| pw148010 [PATCH v2 3/3] usertools/dpdk-devbind: add bind/unbind for platform device 0-day Robot
2024-11-06  4:32 ` |SUCCESS| pw148008-148010 [PATCH] [v2,3/3] usertools/dpdk-devbind: a dpdklab
2024-11-06  4:34 ` dpdklab
2024-11-06  4:36 ` dpdklab
2024-11-06  4:37 ` dpdklab
2024-11-06  4:41 ` dpdklab
2024-11-06  4:55 ` dpdklab
2024-11-06  5:07 ` dpdklab
2024-11-06  5:24 ` |FAILURE| " dpdklab
2024-11-06  7:54 ` dpdklab [this message]

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=672b2099.050a0220.c9ab3.3d62SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=liwencheng@phytium.com.cn \
    --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).