automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: vanshika.shukla@nxp.com, zhoumin@loongson.cn
Subject: |FAILURE| pw154958-154965 [v6 8/8] bus/dpaa: optimize qman enqueue check
Date: Wed, 2 Jul 2025 17:56:46 +0800	[thread overview]
Message-ID: <202507020956.5629ukLM1328809@localhost.localdomain> (raw)
In-Reply-To: <20250702101026.3301762-9-vanshika.shukla@nxp.com>

Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/154965

_ninja build failure_

Submitter: Vanshika Shukla <vanshika.shukla@nxp.com>
Date: Wed,  2 Jul 2025 15:40:19 +0530
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: b18c543ec30729ccc7708a6e064a1f9db5d8c11f

154958-154965 --> ninja build failed

Test environment and result as below:

+---------------------+----------------+
|     Environment     | compilation    |
+---------------------+----------------+
| Loongnix-Server 8.3 | FAIL           |
+---------------------+----------------+

Loongnix-Server 8.3
    Kernel: 4.19.190+
    Compiler: gcc 8.3


Ninja build logs:
-------------------------------BEGIN LOGS----------------------------
FAILED: drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_dpaa_bus.c.o
cc -Idrivers/libtmp_rte_bus_dpaa.a.p -Idrivers -I../drivers -Idrivers/bus/dpaa -I../drivers/bus/dpaa -I../drivers/bus/dpaa/base -I../drivers/bus/dpaa/include -I../drivers/bus/dpaa/base/qbman -Ilib/eal/common -I../lib/eal/common -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/loongarch/include -I../lib/eal/loongarch/include -I../kernel/linux -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 -Idrivers/common/dpaax -I../drivers/common/dpaax -I../drivers/common/dpaax/caamflib -Ilib/eventdev -I../lib/eventdev -Ilib/ring -I../lib/ring -Ilib/ethdev -I../lib/ethdev -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/meter -I../lib/meter -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Ilib/timer -I../lib/timer -Ilib/cryptodev -I../lib/cryptodev -Ilib/dmadev -I../lib/dmadev -fdiagnostics-co
 lor=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c11 -O3 -include rte_config.h -Wvla -Wcast-qual -Wdeprecated -Wformat -Wformat-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 -D_GNU_SOURCE -fPIC -march=loongarch64 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-cast-qual -Wno-pointer-arith -DRTE_LOG_DEFAULT_LOGTYPE=bus.dpaa -MD -MQ drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_dpaa_bus.c.o -MF drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_dpaa_bus.c.o.d -o drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_dpaa_bus.c.o -c ../drivers/bus/dpaa/dpaa_bus.c
In file included from ../lib/eal/common/eal_export.h:8,
from ../drivers/bus/dpaa/dpaa_bus.c:18:
./lib/eal/include/rte_common.h:348:2: error: ‘RTE_PRIORITY_102’ undeclared here (not in a function); did you mean ‘RTE_PRIORITY_BUS’?
RTE_PRIORITY_ ## prio
^~~~~~~~~~~~~
./lib/eal/include/rte_common.h:408:39: note: in expansion of macro ‘RTE_PRIO’
static void __attribute__((destructor(RTE_PRIO(prio)), used)) func(void)
^~~~~~~~
./drivers/bus/dpaa/dpaa_bus.c:920:1: note: in expansion of macro ‘RTE_FINI_PRIO’
RTE_FINI_PRIO(dpaa_cleanup, 102)
^~~~~~~~~~~~~
./drivers/bus/dpaa/dpaa_bus.c: In function ‘dpaa_cleanup’:
./drivers/bus/dpaa/dpaa_bus.c:921:1: error: expected declaration specifiers before ‘dpaa_cleanup’
dpaa_cleanup(void)
^~~~~~~~~~~~
./drivers/bus/dpaa/dpaa_bus.c:938:28: error: storage class specified for parameter ‘rte_dpaa_bus’
static struct rte_dpaa_bus rte_dpaa_bus = {
^~~~~~~~~~~~
./drivers/bus/dpaa/dpaa_bus.c:938:15: error: parameter ‘rte_dpaa_bus’ is initialized
static struct rte_dpaa_bus rte_dpaa_bus = {
^~~~~~~~~~~~
In file included from ../drivers/bus/dpaa/dpaa_bus.c:34:
./lib/eal/include/bus_driver.h:290:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token
{ ^~
(bus).name = RTE_STR(nm);
./lib/eal/include/bus_driver.h:290:1: note: in definition of macro ‘RTE_REGISTER_BUS’
{ ^~
(bus).name = RTE_STR(nm);
./drivers/bus/dpaa/dpaa_bus.c:955:54: error: expected declaration specifiers before ‘;’ token
RTE_REGISTER_BUS(FSL_DPAA_BUS_NAME, rte_dpaa_bus.bus);
^
In file included from ../lib/eal/include/rte_debug.h:17,
from ../lib/eal/include/rte_bitops.h:23,
from ../lib/eal/include/rte_interrupts.h:10,
from ../drivers/bus/dpaa/dpaa_bus.c:21:
./lib/log/rte_log.h:482:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token
{ ^
./lib/log/rte_log.h:509:2: note: in expansion of macro ‘RTE_LOG_REGISTER_IMPL’
RTE_LOG_REGISTER_IMPL(type, RTE_STR(RTE_LOG_DEFAULT_LOGTYPE), level)
^~~~~~~~~~~~~~~~~~~~~
./drivers/bus/dpaa/dpaa_bus.c:956:1: note: in expansion of macro ‘RTE_LOG_REGISTER_DEFAULT’
RTE_LOG_REGISTER_DEFAULT(dpaa_logtype_bus, NOTICE);
^~~~~~~~~~~~~~~~~~~~~~~~
./drivers/bus/dpaa/dpaa_bus.c:956:51: error: expected declaration specifiers before ‘;’ token
RTE_LOG_REGISTER_DEFAULT(dpaa_logtype_bus, NOTICE);
^
In file included from ../lib/eal/common/eal_export.h:8,
from ../drivers/bus/dpaa/dpaa_bus.c:18:
./drivers/bus/dpaa/dpaa_bus.c:920:15: error: old-style parameter declarations in prototyped function definition
RTE_FINI_PRIO(dpaa_cleanup, 102)
^~~~~~~~~~~~
./lib/eal/include/rte_common.h:408:63: note: in definition of macro ‘RTE_FINI_PRIO’
static void __attribute__((destructor(RTE_PRIO(prio)), used)) func(void)
^~~~
./drivers/bus/dpaa/dpaa_bus.c:956: error: expected ‘{’ at end of input
RTE_LOG_REGISTER_DEFAULT(dpaa_logtype_bus, NOTICE);

[569/2983] Linking static target drivers/librte_common_cpt.a
[570/2983] Generating rte_bus_auxiliary.pmd.c with a custom command
[571/2983] Compiling C object drivers/librte_common_octeontx.a.p/meson-generated_.._rte_common_octeontx.pmd.c.o
[572/2983] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_bman.c.o
[573/2983] Compiling C object drivers/librte_common_octeontx.so.25.2.p/meson-generated_.._rte_common_octeontx.pmd.c.o
[574/2983] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_qman_driver.c.o
[575/2983] Compiling C object drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_mc_dpdmai.c.o
[576/2983] Compiling C object drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_mc_dpio.c.o
[577/2983] Generating rte_bus_cdx.pmd.c with a custom command
[578/2983] Compiling C object drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_mc_dprc.c.o
[579/2983] Compiling C object drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_mc_mc_sys.c.o
[580/2983] Generating rte_common_dpaax.pmd.c with a custom command
[581/2983] Generating symbol file lib/librte_mbuf.so.25.2.p/librte_mbuf.so.25.2.symbols
[582/2983] Generating eventdev.sym_chk with a custom command (wrapped by meson to capture output)
[583/2983] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_process.c.o
[584/2983] Compiling C object drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_fslmc_bus.c.o
[585/2983] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_ctl.c.o
[586/2983] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_fman_fman.c.o
[587/2983] Compiling C object lib/librte_ethdev.a.p/ethdev_rte_ethdev.c.o
[588/2983] Compiling C object drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_portal_dpaa2_hw_dpbp.c.o
[589/2983] Generating table.sym_chk with a custom command (wrapped by meson to capture output)
[590/2983] Compiling C object drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_portal_dpaa2_hw_dpci.c.o
[591/2983] Generating port.sym_chk with a custom command (wrapped by meson to capture output)
[592/2983] Generating node.sym_chk with a custom command (wrapped by meson to capture output)
[593/2983] Compiling C object drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_portal_dpaa2_hw_dpio.c.o
[594/2983] Generating graph.sym_chk with a custom command (wrapped by meson to capture output)
[595/2983] Generating rte_common_ionic.sym_chk with a custom command (wrapped by meson to capture output)
[596/2983] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_pipeline_spec.c.o
[597/2983] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_table_action.c.o
[598/2983] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_qman.c.o
[599/2983] Compiling C object lib/librte_vhost.a.p/vhost_vhost_crypto.c.o
[600/2983] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_pipeline.c.o
[601/2983] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------


       reply	other threads:[~2025-07-02 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250702101026.3301762-9-vanshika.shukla@nxp.com>
2025-07-02  9:56 ` qemudev [this message]
2025-07-02 10:10 ` |SUCCESS| pw154965 " checkpatch
2025-07-02 11:03 ` |FAILURE| " 0-day Robot

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=202507020956.5629ukLM1328809@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=test-report@dpdk.org \
    --cc=vanshika.shukla@nxp.com \
    --cc=zhoumin@loongson.cn \
    /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).