From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Jie Liu <liujie5@linkdatatechnology.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw146333 [PATCH] net/sxe: add build and doc infrastructure
Date: Tue, 22 Oct 2024 11:15:01 +0800 [thread overview]
Message-ID: <202410220315.49M3F17L2036664@localhost.localdomain> (raw)
In-Reply-To: <20241020024203.441192-1-liujie5@linkdatatechnology.com>
Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/146333
_ninja build failure_
Submitter: Jie Liu <liujie5@linkdatatechnology.com>
Date: Sat, 19 Oct 2024 19:42:03 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 5bb17458f32befba8a2cccd9553ea65cd8b99581
146333 --> 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/rte_net_sxe.sym_chk
/usr/local/bin/meson --internal exe --capture drivers/rte_net_sxe.sym_chk -- /home/zhoumin/gh_dpdk/buildtools/check-symbols.sh /home/zhoumin/gh_dpdk/drivers/net/sxe/version.map drivers/librte_net_sxe.a
--- stderr ---
[1824/2548] Generating rte_net_ngbe.pmd.c with a custom command
[1825/2548] Linking static target drivers/libtmp_rte_net_qede.a
[1826/2548] Generating rte_raw_cnxk_gpio.pmd.c with a custom command
[1827/2548] Compiling C object drivers/libtmp_rte_raw_skeleton.a.p/raw_skeleton_skeleton_rawdev.c.o
[1828/2548] Compiling C object drivers/libtmp_rte_crypto_bcmfs.a.p/crypto_bcmfs_bcmfs_sym_session.c.o
[1829/2548] Compiling C object drivers/libtmp_rte_crypto_bcmfs.a.p/crypto_bcmfs_hw_bcmfs5_rm.c.o
[1830/2548] Compiling C object drivers/libtmp_rte_crypto_bcmfs.a.p/crypto_bcmfs_hw_bcmfs4_rm.c.o
[1831/2548] Compiling C object drivers/libtmp_rte_crypto_bcmfs.a.p/crypto_bcmfs_bcmfs_sym.c.o
[1832/2548] Compiling C object drivers/libtmp_rte_crypto_caam_jr.a.p/crypto_caam_jr_caam_jr_capabilities.c.o
[1833/2548] Compiling C object drivers/libtmp_rte_raw_skeleton.a.p/raw_skeleton_skeleton_rawdev_test.c.o
[1834/2548] Generating rte_net_vhost.pmd.c with a custom command
[1835/2548] Compiling C object drivers/raw/ifpga/base/libifpga_rawdev_base.a.p/opae_intel_max10.c.o
[1836/2548] Compiling C object drivers/libtmp_rte_crypto_bcmfs.a.p/crypto_bcmfs_bcmfs_sym_pmd.c.o
[1837/2548] Compiling C object drivers/libtmp_rte_crypto_ccp.a.p/crypto_ccp_ccp_pmd_ops.c.o
[1838/2548] Compiling C object drivers/libtmp_rte_crypto_ccp.a.p/crypto_ccp_rte_ccp_pmd.c.o
[1839/2548] Generating rte_net_thunderx.pmd.c with a custom command
[1840/2548] Compiling C object drivers/libtmp_rte_crypto_bcmfs.a.p/crypto_bcmfs_bcmfs_sym_engine.c.o
[1841/2548] Compiling C object drivers/libtmp_rte_crypto_caam_jr.a.p/crypto_caam_jr_caam_jr_hw.c.o
[1842/2548] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn9k_cryptodev.c.o
[1843/2548] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn10k_cryptodev.c.o
[1844/2548] Compiling C object drivers/libtmp_rte_crypto_caam_jr.a.p/crypto_caam_jr_caam_jr_uio.c.o
[1845/2548] Compiling C object drivers/libtmp_rte_crypto_ccp.a.p/crypto_ccp_ccp_dev.c.o
[1846/2548] Compiling C object drivers/libtmp_rte_net_txgbe.a.p/net_txgbe_txgbe_ethdev.c.o
[1847/2548] Generating rte_net_ixgbe.sym_chk with a custom command (wrapped by meson to capture output)
[1848/2548] Compiling C object drivers/libtmp_rte_raw_ntb.a.p/raw_ntb_ntb.c.o
[1849/2548] Compiling C object drivers/libtmp_rte_net_vmxnet3.a.p/net_vmxnet3_vmxnet3_rxtx.c.o
[1850/2548] Compiling C object drivers/libtmp_rte_net_virtio.a.p/net_virtio_virtio_rxtx.c.o
[1851/2548] Compiling C object drivers/libtmp_rte_net_txgbe.a.p/net_txgbe_txgbe_rxtx.c.o
[1852/2548] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn10k_cryptodev_ops.c.o
[1853/2548] Compiling C object drivers/libtmp_rte_crypto_ccp.a.p/crypto_ccp_ccp_crypto.c.o
[1854/2548] Compiling C object drivers/libtmp_rte_crypto_caam_jr.a.p/crypto_caam_jr_caam_jr.c.o
[1855/2548] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1856/2548] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn9k_cryptodev_ops.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------
prev parent reply other threads:[~2024-10-22 3:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241020024203.441192-1-liujie5@linkdatatechnology.com>
2024-10-20 2:42 ` |SUCCESS| " checkpatch
2024-10-20 3:43 ` |FAILURE| " 0-day Robot
2024-10-20 10:12 ` dpdklab
2024-10-21 3:06 ` qemudev
2024-10-22 3:15 ` qemudev [this message]
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=202410220315.49M3F17L2036664@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=liujie5@linkdatatechnology.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).