automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Srikanth Yalavarthi <syalavarthi@marvell.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw135789-135791 [PATCH 4/4] ml/cnxk: add adapter dequeue function
Date: Sun, 7 Jan 2024 23:41:05 +0800	[thread overview]
Message-ID: <202401071541.407Ff5si3008739@localhost.localdomain> (raw)
In-Reply-To: <20240107154013.4676-5-syalavarthi@marvell.com>

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

_ninja build failure_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Sun, 7 Jan 2024 07:40:10 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 6ef07151aac4b4d9601d547f94a996d1c71b3871

135789-135791 --> 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_ml_cnxk.a.p/ml_cnxk_cn10k_ml_ops.c.o
cc -Idrivers/libtmp_rte_ml_cnxk.a.p -Idrivers -I../drivers -Idrivers/ml/cnxk -I../drivers/ml/cnxk -Ilib/mldev -I../lib/mldev -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 -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/mbuf -I../lib/mbuf -Idrivers/common/cnxk -I../drivers/common/cnxk -Idrivers/bus/pci -I../drivers/bus/pci -Ilib/net -I../lib/net -Ilib/ethdev -I../lib/ethdev -Ilib/meter -I../lib/meter -Ilib/pci -I../lib/pci -I../drivers/bus/pci/linux -Ilib/security -I../lib/security -Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu -Ilib/hash -I../lib/hash -Ilib/eventdev -I../lib/eventdev -Ilib/timer -I../lib/timer -Ilib/dmadev -I../lib/dmadev -fdiagnostics-c
 olor=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 -UCNXK_ML_DEV_DEBUG -DRTE_LOG_DEFAULT_LOGTYPE=pmd.ml.cnxk -MD -MQ drivers/libtmp_rte_ml_cnxk.a.p/ml_cnxk_cn10k_ml_ops.c.o -MF drivers/libtmp_rte_ml_cnxk.a.p/ml_cnxk_cn10k_ml_ops.c.o.d -o drivers/libtmp_rte_ml_cnxk.a.p/ml_cnxk_cn10k_ml_ops.c.o -c ../drivers/ml/cnxk/cn10k_ml_ops.c
./drivers/ml/cnxk/cn10k_ml_ops.c:5:10: fatal error: rte_event_ml_adapter.h: No such file or directory
#include <rte_event_ml_adapter.h>
^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
[1813/2424] Linking target drivers/librte_compress_zlib.so.24.1
[1814/2424] Compiling C object drivers/libtmp_rte_crypto_virtio.a.p/crypto_virtio_virtio_rxtx.c.o
[1815/2424] Compiling C object drivers/libtmp_rte_crypto_dpaa2_sec.a.p/crypto_dpaa2_sec_dpaa2_sec_raw_dp.c.o
[1816/2424] Compiling C object drivers/libtmp_rte_crypto_null.a.p/crypto_null_null_crypto_pmd.c.o
[1817/2424] Generating rte_net_vmxnet3.pmd.c with a custom command
[1818/2424] Compiling C object drivers/libtmp_rte_crypto_virtio.a.p/crypto_virtio_virtqueue.c.o
[1819/2424] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_failover.c.o
[1820/2424] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_roundrobin.c.o
[1821/2424] Generating rte_net_vhost.sym_chk with a custom command (wrapped by meson to capture output)
[1822/2424] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_pkt_size_distr.c.o
[1823/2424] Generating rte_net_qede.pmd.c with a custom command
[1824/2424] Generating rte_crypto_nitrox.pmd.c with a custom command
[1825/2424] Generating rte_raw_ntb.pmd.c with a custom command
[1826/2424] Compiling C object drivers/libtmp_rte_crypto_virtio.a.p/crypto_virtio_virtio_cryptodev.c.o
[1827/2424] Generating rte_regex_cn9k.pmd.c with a custom command
[1828/2424] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec_raw_dp.c.o
[1829/2424] Compiling C object drivers/libtmp_rte_ml_cnxk.a.p/ml_cnxk_cn10k_ml_dev.c.o
[1830/2424] Compiling C object drivers/libtmp_rte_ml_cnxk.a.p/ml_cnxk_cn10k_ml_ocm.c.o
[1831/2424] Generating rte_net_ixgbe.sym_chk with a custom command (wrapped by meson to capture output)
[1832/2424] Compiling C object drivers/libtmp_rte_ml_cnxk.a.p/ml_cnxk_cn10k_ml_model.c.o
[1833/2424] Compiling C object drivers/libtmp_rte_net_txgbe.a.p/net_txgbe_txgbe_rxtx.c.o
[1834/2424] Compiling C object drivers/libtmp_rte_compress_octeontx.a.p/compress_octeontx_otx_zip_pmd.c.o
[1835/2424] Compiling C object drivers/libtmp_rte_net_virtio.a.p/net_virtio_virtio_rxtx.c.o
[1836/2424] Compiling C object drivers/libtmp_rte_crypto_ccp.a.p/crypto_ccp_ccp_crypto.c.o
[1837/2424] Compiling C object drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o
[1838/2424] Compiling C object drivers/libtmp_rte_crypto_caam_jr.a.p/crypto_caam_jr_caam_jr.c.o
[1839/2424] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_multicore.c.o
[1840/2424] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec.c.o
[1841/2424] Compiling C object drivers/libtmp_rte_crypto_dpaa2_sec.a.p/crypto_dpaa2_sec_dpaa2_sec_dpseci.c.o
[1842/2424] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1843/2424] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn9k_cryptodev_ops.c.o
[1844/2424] Compiling C object drivers/libtmp_rte_crypto_octeontx.a.p/crypto_octeontx_otx_cryptodev_ops.c.o
[1845/2424] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn10k_cryptodev_ops.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------


       reply	other threads:[~2024-01-07 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240107154013.4676-5-syalavarthi@marvell.com>
2024-01-07 15:41 ` qemudev [this message]
2024-01-07 15:41 ` |SUCCESS| pw135791 " checkpatch
2024-01-07 18:31 |FAILURE| pw135789-135791 [PATCH] [4/4] " 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=202401071541.407Ff5si3008739@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=syalavarthi@marvell.com \
    --cc=test-report@dpdk.org \
    --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).