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,
	Nicolas Chautru <nicolas.chautru@intel.com>
Subject: |FAILURE| pw132309-132320 [PATCH] [v4,12/12] baseband/acc: add confi
Date: Thu, 05 Oct 2023 00:07:33 -0700 (PDT)	[thread overview]
Message-ID: <651e60b5.050a0220.61a04.383aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/132320

_Testing issues_

Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Thursday, October 05 2023 02:18:54 
DPDK git baseline: Repo:dpdk-next-baseband
  Branch: master
  CommitID:fbafb3676c482dab60c0b5465b47f2ea33893a36

132309-132320 --> testing fail

Test environment and result as below:

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

==== 20 line log output for FreeBSD 13 (dpdk_meson_compile): ====
[1437/1777] Linking target drivers/librte_event_opdl.so.24.0
[1438/1777] Generating drivers/rte_crypto_scheduler.sym_chk with a custom command (wrapped by meson to capture output)
[1439/1777] Compiling C object drivers/librte_event_sw.a.p/meson-generated_.._rte_event_sw.pmd.c.o
[1440/1777] Compiling C object drivers/librte_event_sw.so.24.0.p/meson-generated_.._rte_event_sw.pmd.c.o
[1441/1777] Linking static target drivers/librte_event_sw.a
[1442/1777] Linking target drivers/librte_crypto_scheduler.so.24.0
[1443/1777] Linking target drivers/librte_event_sw.so.24.0
[1444/1777] Compiling C object drivers/libtmp_rte_baseband_acc.a.p/baseband_acc_rte_vrb_pmd.c.o
FAILED: drivers/libtmp_rte_baseband_acc.a.p/baseband_acc_rte_vrb_pmd.c.o
ccache cc -Idrivers/libtmp_rte_baseband_acc.a.p -Idrivers -I../drivers -Idrivers/baseband/acc -I../drivers/baseband/acc -Ilib/bbdev -I../lib/bbdev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/freebsd/include -I../lib/eal/freebsd/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/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/bsd -Ilib/pci -I../lib/pci -fcolor-diagnostics -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-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwri
 te-strings -Wno-address-of-packed-member -Wno-missing-field-initializers -D_GNU_SOURCE -D__BSD_VISIBLE -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -DRTE_LOG_DEFAULT_LOGTYPE=pmd.bb.acc -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ drivers/libtmp_rte_baseband_acc.a.p/baseband_acc_rte_vrb_pmd.c.o -MF drivers/libtmp_rte_baseband_acc.a.p/baseband_acc_rte_vrb_pmd.c.o.d -o drivers/libtmp_rte_baseband_acc.a.p/baseband_acc_rte_vrb_pmd.c.o -c ../drivers/baseband/acc/rte_vrb_pmd.c
../drivers/baseband/acc/rte_vrb_pmd.c:210:1: error: unused function 'vrb_device_fft_win' [-Werror,-Wunused-function]
vrb_device_fft_win(struct rte_bbdev *dev)
^
1 error generated.
[1445/1777] Compiling C object drivers/libtmp_rte_baseband_la12xx.a.p/baseband_la12xx_bbdev_la12xx.c.o
[1446/1777] Compiling C object drivers/libtmp_rte_baseband_fpga_lte_fec.a.p/baseband_fpga_lte_fec_fpga_lte_fec.c.o
[1447/1777] Compiling C object drivers/libtmp_rte_baseband_fpga_5gnr_fec.a.p/baseband_fpga_5gnr_fec_rte_fpga_5gnr_fec.c.o
[1448/1777] Generating drivers/rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
[1449/1777] Compiling C object drivers/libtmp_rte_baseband_acc.a.p/baseband_acc_rte_acc100_pmd.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

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

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

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

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

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

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

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

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

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-05  7:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  7:07 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-05  7:54 dpdklab
2023-10-05  7:21 dpdklab
2023-10-05  7:00 dpdklab
2023-10-05  6:43 dpdklab
2023-10-05  6:33 dpdklab
2023-10-05  6:30 dpdklab
2023-10-05  6:17 dpdklab
2023-10-05  6:12 dpdklab
2023-10-05  6:04 dpdklab
2023-10-05  5:52 dpdklab
2023-10-05  5:51 dpdklab
2023-10-05  5:46 dpdklab
2023-10-05  5:40 dpdklab
2023-10-05  5:31 dpdklab
2023-10-05  5:30 dpdklab
2023-10-05  5:30 dpdklab
2023-10-05  5:29 dpdklab
2023-10-05  5:28 dpdklab
2023-10-05  5:16 dpdklab
2023-10-05  5:12 dpdklab
2023-10-05  5:01 dpdklab
2023-10-05  4:56 dpdklab
2023-10-05  4:26 dpdklab
2023-10-05  4:22 dpdklab
2023-10-05  4:05 dpdklab
2023-10-05  3:27 dpdklab
2023-10-05  3:22 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=651e60b5.050a0220.61a04.383aSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=nicolas.chautru@intel.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).