automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Vamsi Krishna <vattunuru@marvell.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw144983 [PATCH v0 1/1] dma/cnxk: support dma queue priority configuration
Date: Thu, 3 Oct 2024 20:58:04 +0800	[thread overview]
Message-ID: <202410031258.493Cw4bG3436640@localhost.localdomain> (raw)
In-Reply-To: <20241003132455.1374860-1-vattunuru@marvell.com>

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

_ninja build failure_

Submitter: Vamsi Krishna <vattunuru@marvell.com>
Date: Thu, 3 Oct 2024 18:54:55 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
  Branch: for-next-net
  CommitID: 51aa080ee3c36a5ec9a2737c1a46ddd5bb725159

144983 --> 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_dma_cnxk.a.p/dma_cnxk_cnxk_dmadev.c.o
cc -Idrivers/libtmp_rte_dma_cnxk.a.p -Idrivers -I../drivers -Idrivers/dma/cnxk -I../drivers/dma/cnxk -Idrivers/event/cnxk -I../drivers/event/cnxk -Ilib/dmadev -I../lib/dmadev -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 -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 -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/common/cnxk -I../drivers/common/cnxk -Ilib/net -I../lib/net -Ilib/ethdev -I../lib/ethdev -Ilib/meter -I../lib/meter -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/security -I../lib/security -Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu -Ilib/eventdev -I../lib/eventdev -Ilib/hash -I../lib/hash -Ilib/timer -I../lib/
 timer -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -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 -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-uninitialized -DRTE_LOG_DEFAULT_LOGTYPE=pmd.dma.cnxk -MD -MQ drivers/libtmp_rte_dma_cnxk.a.p/dma_cnxk_cnxk_dmadev.c.o -MF drivers/libtmp_rte_dma_cnxk.a.p/dma_cnxk_cnxk_dmadev.c.o.d -o drivers/libtmp_rte_dma_cnxk.a.p/dma_cnxk_cnxk_dmadev.c.o -c ../drivers/dma/cnxk/cnxk_dmadev.c
./drivers/dma/cnxk/cnxk_dmadev.c: In function ‘cnxk_dmadev_info_get’:
./drivers/dma/cnxk/cnxk_dmadev.c:24:25: error: ‘RTE_DMA_CAPA_PRI_POLICY_SP’ undeclared (first use in this function); did you mean ‘RTE_DMA_CAPA_OPS_COPY_SG’?
dev_info->dev_capa |= RTE_DMA_CAPA_PRI_POLICY_SP;
^~~~~~~~~~~~~~~~~~~~~~~~~~
RTE_DMA_CAPA_OPS_COPY_SG
./drivers/dma/cnxk/cnxk_dmadev.c:24:25: note: each undeclared identifier is reported only once for each function it appears in
./drivers/dma/cnxk/cnxk_dmadev.c:25:11: error: ‘struct rte_dma_info’ has no member named ‘nb_priorities’
dev_info->nb_priorities = CNXK_DPI_MAX_PRI;
^~
./drivers/dma/cnxk/cnxk_dmadev.c: In function ‘cnxk_dmadev_configure’:
./drivers/dma/cnxk/cnxk_dmadev.c:115:30: error: ‘const struct rte_dma_conf’ has no member named ‘priority’
dpivf->rdpi.priority = conf->priority;
^~
[713/2530] Compiling C object drivers/libtmp_rte_net_ark.a.p/net_ark_ark_ddm.c.o
[714/2530] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen4.c.o
[715/2530] Compiling C object drivers/libtmp_rte_mempool_octeontx.a.p/mempool_octeontx_octeontx_fpavf.c.o
[716/2530] Compiling C object drivers/libtmp_rte_mempool_dpaa2.a.p/mempool_dpaa2_dpaa2_hw_mempool.c.o
[717/2530] Compiling C object drivers/libtmp_rte_mempool_dpaa.a.p/mempool_dpaa_dpaa_mempool.c.o
[718/2530] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o
[719/2530] Compiling C object drivers/libtmp_rte_dma_odm.a.p/dma_odm_odm_dmadev.c.o
[720/2530] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_session.c.o
[721/2530] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen3.c.o
[722/2530] Generating rte_mempool_cnxk.pmd.c with a custom command
[723/2530] Generating rte_mempool_stack.pmd.c with a custom command
[724/2530] Compiling C object drivers/libtmp_rte_dma_dpaa.a.p/dma_dpaa_dpaa_qdma.c.o
[725/2530] Compiling C object drivers/libtmp_rte_net_ark.a.p/net_ark_ark_ethdev.c.o
[726/2530] Compiling C object drivers/libtmp_rte_crypto_dpaa2_sec.a.p/crypto_dpaa2_sec_dpaa2_sec_raw_dp.c.o
[727/2530] Generating rte_common_nitrox.sym_chk with a custom command (wrapped by meson to capture output)
[728/2530] Compiling C object drivers/libtmp_rte_net_ark.a.p/net_ark_ark_ethdev_rx.c.o
[729/2530] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec_raw_dp.c.o
[730/2530] Compiling C object drivers/libtmp_rte_net_af_packet.a.p/net_af_packet_rte_eth_af_packet.c.o
[731/2530] Generating rte_common_nfp.sym_chk with a custom command (wrapped by meson to capture output)
[732/2530] Compiling C object drivers/libtmp_rte_dma_cnxk.a.p/dma_cnxk_cnxk_dmadev_fp.c.o
[733/2530] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_sym_pmd_gen1.c.o
[734/2530] Compiling C object drivers/libtmp_rte_mempool_bucket.a.p/mempool_bucket_rte_mempool_bucket.c.o
[735/2530] Compiling C object drivers/libtmp_rte_dma_dpaa2.a.p/dma_dpaa2_dpaa2_qdma.c.o
[736/2530] Generating rte_common_idpf.sym_chk with a custom command (wrapped by meson to capture output)
[737/2530] Compiling C object drivers/libtmp_rte_dma_skeleton.a.p/dma_skeleton_skeleton_dmadev.c.o
[738/2530] Generating rte_common_cnxk.pmd.c with a custom command
[739/2530] Generating rte_bus_fslmc.sym_chk with a custom command (wrapped by meson to capture output)
[740/2530] Generating rte_bus_dpaa.sym_chk with a custom command (wrapped by meson to capture output)
[741/2530] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_pipeline.c.o
[742/2530] Generating eal.sym_chk with a custom command (wrapped by meson to capture output)
[743/2530] Generating ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[744/2530] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec.c.o
[745/2530] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------


       reply	other threads:[~2024-10-03 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241003132455.1374860-1-vattunuru@marvell.com>
2024-10-03 12:58 ` qemudev [this message]
2024-10-03 13:28 ` |SUCCESS| " checkpatch
2024-10-03 13:48 ` |FAILURE| pw144983 [PATCH] [v0, " dpdklab
2024-10-03 14:07 ` |FAILURE| pw144983 [PATCH v0 " 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=202410031258.493Cw4bG3436640@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=test-report@dpdk.org \
    --cc=vattunuru@marvell.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).