From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Lukas Sismis <sismis@cesnet.cz>, zhoumin@loongson.cn
Subject: |FAILURE| pw147605 [PATCH] net/bonding: make bonding functions stable
Date: Tue, 29 Oct 2024 22:10:51 +0800 [thread overview]
Message-ID: <202410291410.49TEAp6s1023232@localhost.localdomain> (raw)
In-Reply-To: <20241029144251.269529-1-sismis@cesnet.cz>
Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/147605
_ninja build failure_
Submitter: Lukas Sismis <sismis@cesnet.cz>
Date: Tue, 29 Oct 2024 15:42:51 +0100
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: b7f037995ce4f543136e135b9f14a035f31ddeed
147605 --> 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_bond.sym_chk
/usr/local/bin/meson --internal exe --capture drivers/rte_net_bond.sym_chk -- /home/zhoumin/gh_dpdk/buildtools/check-symbols.sh /home/zhoumin/gh_dpdk/drivers/net/bonding/version.map drivers/librte_net_bond.a
--- stderr ---
rte_eth_bond_active_members_get is not flagged as experimental
but is listed in version map
Please add __rte_experimental to the definition of rte_eth_bond_active_members_get
rte_eth_bond_member_add is not flagged as experimental
but is listed in version map
Please add __rte_experimental to the definition of rte_eth_bond_member_add
rte_eth_bond_member_remove is not flagged as experimental
but is listed in version map
Please add __rte_experimental to the definition of rte_eth_bond_member_remove
rte_eth_bond_members_get is not flagged as experimental
but is listed in version map
Please add __rte_experimental to the definition of rte_eth_bond_members_get
[1256/2540] Generating symbol file drivers/librte_mempool_octeontx.so.25.0.p/librte_mempool_octeontx.so.25.0.symbols
[1257/2540] Generating rte_net_ena.pmd.c with a custom command
[1258/2540] Compiling C object drivers/libtmp_rte_net_hinic.a.p/net_hinic_hinic_pmd_ethdev.c.o
[1259/2540] Compiling C object drivers/net/hinic/base/libhinic_base.a.p/hinic_pmd_hwdev.c.o
[1260/2540] Compiling C object drivers/libtmp_rte_net_gve.a.p/net_gve_gve_tx.c.o
[1261/2540] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_acl.c.o
[1262/2540] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_ops.c.o
[1263/2540] Compiling C object drivers/net/hinic/base/libhinic_base.a.p/hinic_pmd_niccfg.c.o
[1264/2540] Generating symbol file lib/librte_hash.so.25.0.p/librte_hash.so.25.0.symbols
[1265/2540] Generating symbol file lib/librte_rib.so.25.0.p/librte_rib.so.25.0.symbols
[1266/2540] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_tm.c.o
[1267/2540] Compiling C object drivers/libtmp_rte_net_hinic.a.p/net_hinic_hinic_pmd_rx.c.o
[1268/2540] Generating symbol file lib/librte_ethdev.so.25.0.p/librte_ethdev.so.25.0.symbols
[1269/2540] Generating rte_net_dpaa2.pmd.c with a custom command
[1270/2540] Generating symbol file drivers/librte_common_cpt.so.25.0.p/librte_common_cpt.so.25.0.symbols
[1271/2540] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_generic_flow.c.o
[1272/2540] Generating symbol file lib/librte_security.so.25.0.p/librte_security.so.25.0.symbols
[1273/2540] Compiling C object drivers/libtmp_rte_net_fm10k.a.p/net_fm10k_fm10k_ethdev.c.o
[1274/2540] Generating symbol file drivers/librte_common_nfp.so.25.0.p/librte_common_nfp.so.25.0.symbols
[1275/2540] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_fsub.c.o
[1276/2540] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_hash.c.o
[1277/2540] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_controlq.c.o
[1278/2540] Compiling C object drivers/libtmp_rte_net_hinic.a.p/net_hinic_hinic_pmd_tx.c.o
[1279/2540] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_ipsec_crypto.c.o
[1280/2540] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_fdir.c.o
[1281/2540] Generating rte_net_enic.pmd.c with a custom command
[1282/2540] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[1283/2540] Generating rte_net_bnxt.pmd.c with a custom command
[1284/2540] Compiling C object drivers/libtmp_rte_net_hinic.a.p/net_hinic_hinic_pmd_flow.c.o
[1285/2540] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_vchnl.c.o
[1286/2540] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_ethdev.c.o
[1287/2540] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_rxtx.c.o
[1288/2540] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------
next parent reply other threads:[~2024-10-29 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241029144251.269529-1-sismis@cesnet.cz>
2024-10-29 14:10 ` qemudev [this message]
2024-10-29 14:43 ` |SUCCESS| " checkpatch
2024-10-29 15:25 ` |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=202410291410.49TEAp6s1023232@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=sismis@cesnet.cz \
--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).