automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Mingjin Ye <mingjinx.ye@intel.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw134254 [PATCH] vfio: add get device info API
Date: Tue, 14 Nov 2023 18:20:08 +0800	[thread overview]
Message-ID: <202311141020.3AEAK8oE2799425@localhost.localdomain> (raw)
In-Reply-To: <20231114102300.409158-1-mingjinx.ye@intel.com>

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

_ninja build failure_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Tue, 14 Nov 2023 10:23:00 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: fdee0f1b30ae8dfc431465878aae5295372cca6f

134254 --> 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: lib/eal.sym_chk
/usr/bin/meson --internal exe --capture lib/eal.sym_chk -- /home/zhoumin/dpdk/buildtools/check-symbols.sh /home/zhoumin/dpdk/lib/eal/version.map lib/librte_eal.a
rte_vfio_get_device_info is not flagged as experimental
but is listed in version map
Please add __rte_experimental to the definition of rte_vfio_get_device_info
[1006/2420] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_hwrm.c.o
[1007/2420] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_phy.c.o
[1008/2420] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_eal.c.o
[1009/2420] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_res.c.o
[1010/2420] Generating rte_net_enetc.pmd.c with a custom command
[1011/2420] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_base_vnic_dev.c.o
[1012/2420] Compiling C object drivers/libtmp_rte_net_dpaa.a.p/net_dpaa_dpaa_rxtx.c.o
[1013/2420] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_vf_representor.c.o
[1014/2420] Generating rte_net_enetfec.pmd.c with a custom command
[1015/2420] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_args.c.o
[1016/2420] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_flow.c.o
[1017/2420] Compiling C object drivers/libtmp_rte_net_ena.a.p/net_ena_base_ena_com.c.o
[1018/2420] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_flow.c.o
[1019/2420] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_ether.c.o
[1020/2420] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_ich8lan.c.o
[1021/2420] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_ethdev.c.o
[1022/2420] Generating rte_net_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1023/2420] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_bnx2x.c.o
[1024/2420] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_em_rxtx.c.o
[1025/2420] Compiling C object drivers/libtmp_rte_net_bond.a.p/net_bonding_rte_eth_bond_pmd.c.o
[1026/2420] Generating rte_net_cxgbe.pmd.c with a custom command
[1027/2420] Generating ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[1028/2420] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_rxtx.c.o
[1029/2420] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_elink.c.o
[1030/2420] Compiling C object drivers/libtmp_rte_net_ena.a.p/net_ena_ena_ethdev.c.o
[1031/2420] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_igb_rxtx.c.o
[1032/2420] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_fm_flow.c.o
[1033/2420] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_main.c.o
[1034/2420] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_igb_ethdev.c.o
[1035/2420] Generating vhost.sym_chk with a custom command (wrapped by meson to capture output)
[1036/2420] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_rxtx.c.o
[1037/2420] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[1038/2420] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------


       reply	other threads:[~2023-11-14 10:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231114102300.409158-1-mingjinx.ye@intel.com>
2023-11-14 10:20 ` qemudev [this message]
2023-11-14 10:39 ` |SUCCESS| " checkpatch

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=202311141020.3AEAK8oE2799425@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=mingjinx.ye@intel.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).