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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 5bd8d23843b70d5bedff28aa055da857dbd97958
Date: Sun, 11 Aug 2024 06:32:58 -0700 (PDT)	[thread overview]
Message-ID: <66b8bd8a.050a0220.219c10.8c00SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: 23.11-staging

5bd8d23843b70d5bedff28aa055da857dbd97958 --> testing issues

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

Test environment and result as below:

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

==== 20 line log output for Ubuntu 22.04 (ARM) (dpdk_meson_compile): ====
[1014/3119] Linking static target drivers/librte_net_af_packet.a.
[1015/3119] Compiling C object 'drivers/a715181@@rte_net_af_packet@sha/meson-generated_.._rte_net_af_packet.pmd.c.o'.
[1016/3119] Linking target drivers/librte_net_af_packet.so.24.0.
[1017/3119] Compiling C object 'drivers/a715181@@tmp_rte_net_af_xdp@sta/net_af_xdp_rte_eth_af_xdp.c.o'.
FAILED: drivers/a715181@@tmp_rte_net_af_xdp@sta/net_af_xdp_rte_eth_af_xdp.c.o
ccache cc -Idrivers/a715181@@tmp_rte_net_af_xdp@sta -Idrivers -I../drivers -Idrivers/net/af_xdp -I../drivers/net/af_xdp -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 -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/telemetry/../metrics -I../lib/telemetry/../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 -Wformat-nonliteral -Wformat-security -Wmissing-declara
 tions -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 -fPIC -march=armv8.1-a+crc+crypto -mcpu=thunderx2t99 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_NET_AF_XDP_SHARED_UMEM -DETH_AF_XDP_UPDATE_XSKMAP -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.af_xdp -MD -MQ 'drivers/a715181@@tmp_rte_net_af_xdp@sta/net_af_xdp_rte_eth_af_xdp.c.o' -MF 'drivers/a715181@@tmp_rte_net_af_xdp@sta/net_af_xdp_rte_eth_af_xdp.c.o.d' -o 'drivers/a715181@@tmp_rte_net_af_xdp@sta/net_af_xdp_rte_eth_af_xdp.c.o' -c ../drivers/net/af_xdp/rte_eth_af_xdp.c
../drivers/net/af_xdp/rte_eth_af_xdp.c: In function 'xdp_umem_configure':
../drivers/net/af_xdp/rte_eth_af_xdp.c:1138:43: error: storage size of 'range' isn't known
1138 |         struct rte_mempool_mem_range_info range;
|                                           ^~~~~
../drivers/net/af_xdp/rte_eth_af_xdp.c:1170:23: error: implicit declaration of function 'rte_mempool_get_mem_range'; did you mean 'rte_mempool_get_trailer'? [-Werror=implicit-function-declaration]
1170 |                 ret = rte_mempool_get_mem_range(mb_pool, &range);
|                       ^~~~~~~~~~~~~~~~~~~~~~~~~
|                       rte_mempool_get_trailer
../drivers/net/af_xdp/rte_eth_af_xdp.c:1170:23: error: nested extern declaration of 'rte_mempool_get_mem_range' [-Werror=nested-externs]
../drivers/net/af_xdp/rte_eth_af_xdp.c:1138:43: error: unused variable 'range' [-Werror=unused-variable]
1138 |         struct rte_mempool_mem_range_info range;
|                                           ^~~~~
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

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 40 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Ubuntu 22.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.0

Ubuntu 24.04 (ARM)
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-08-11 13:33 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11 13:32 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-11 15:23 dpdklab
2024-08-11 15:17 dpdklab
2024-08-11 15:08 dpdklab
2024-08-11 14:59 dpdklab
2024-08-11 14:53 dpdklab
2024-08-11 14:50 dpdklab
2024-08-11 14:44 dpdklab
2024-08-11 14:40 dpdklab
2024-08-11 14:38 dpdklab
2024-08-11 14:29 dpdklab
2024-08-11 14:20 dpdklab
2024-08-11 14:15 dpdklab
2024-08-11 14:07 dpdklab
2024-08-11 14:06 dpdklab
2024-08-11 14:03 dpdklab
2024-08-11 13:59 dpdklab
2024-08-11 13:56 dpdklab
2024-08-11 13:51 dpdklab
2024-08-11 13:50 dpdklab
2024-08-11 13:48 dpdklab
2024-08-11 13:45 dpdklab
2024-08-11 13:44 dpdklab
2024-08-11 13:42 dpdklab
2024-08-11 13:41 dpdklab
2024-08-11 13:40 dpdklab
2024-08-11 13:40 dpdklab
2024-08-11 13:38 dpdklab
2024-08-11 13:36 dpdklab
2024-08-11 13:35 dpdklab
2024-08-11 13:35 dpdklab
2024-08-11 13:34 dpdklab
2024-08-11 13:34 dpdklab
2024-08-11 13:33 dpdklab
2024-08-11 13:33 dpdklab
2024-08-11 13:32 dpdklab
2024-08-11 13:31 dpdklab
2024-08-11 13:31 dpdklab
2024-08-11 13:30 dpdklab
2024-08-11 13:29 dpdklab
2024-08-11 13:29 dpdklab
2024-08-11 13:25 dpdklab
2024-08-11 13:25 dpdklab
2024-08-11 13:24 dpdklab
2024-08-11 13:24 dpdklab
2024-08-11 13:24 dpdklab
2024-08-11 13:21 dpdklab
2024-08-11 13:20 dpdklab
2024-08-11 13:20 dpdklab
2024-08-11 13:17 dpdklab
2024-08-11 13:16 dpdklab
2024-08-11 13:14 dpdklab
2024-08-11 13:14 dpdklab
2024-08-11 13:13 dpdklab
2024-08-11 13:12 dpdklab
2024-08-11 13:12 dpdklab
2024-08-11 13:12 dpdklab
2024-08-11 13:11 dpdklab
2024-08-11 13:11 dpdklab
2024-08-11 13:11 dpdklab
2024-08-11 13:08 dpdklab
2024-08-11 13:06 dpdklab
2024-08-11 13:03 dpdklab
2024-08-11 13:03 dpdklab
2024-08-11 13:01 dpdklab
2024-08-11 12:59 dpdklab
2024-08-11 12:59 dpdklab
2024-08-11 12:58 dpdklab
2024-08-11 12:58 dpdklab
2024-08-11 12:56 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=66b8bd8a.050a0220.219c10.8c00SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).