automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw138201-138199 [PATCH 3/3] ethdev: import and export data variables for MSVC
Date: Tue, 12 Mar 2024 15:29:04 +0800	[thread overview]
Message-ID: <202403120729.42C7T4m72931604@localhost.localdomain> (raw)
In-Reply-To: <1710229908-31704-4-git-send-email-roretzla@linux.microsoft.com>

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

_ninja build failure_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tue, 12 Mar 2024 00:51:46 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: a86f381b826660e88794754c41d3aec79ce9b87c

138201-138199 --> 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/gh_dpdk/buildtools/check-symbols.sh /home/zhoumin/gh_dpdk/lib/eal/version.map lib/librte_eal.a
Found badly formatted maps:
per_lcore__lcore_id; # MSVC_NO_EXPORT
per_lcore__rte_errno; # MSVC_NO_EXPORT
per_lcore__thread_id; # MSVC_NO_EXPORT
[994/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_base_dpaa2_hw_dpni.c.o
[995/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_sparser.c.o
[996/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_ptp.c.o
[997/2496] Compiling C object drivers/libtmp_rte_net_dpaa.a.p/net_dpaa_dpaa_flow.c.o
[998/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_mc_dprtc.c.o
[999/2496] Compiling C object drivers/libtmp_rte_net_cxgbe.a.p/net_cxgbe_cxgbe_flow.c.o
[1000/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_recycle.c.o
[1001/2496] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_82542.c.o
[1002/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_mc_dpdmux.c.o
[1003/2496] Compiling C object drivers/libtmp_rte_net_cxgbe.a.p/net_cxgbe_cxgbe_ethdev.c.o
[1004/2496] Compiling C object drivers/libtmp_rte_net_bond.a.p/net_bonding_rte_eth_bond_8023ad.c.o
[1005/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_tm.c.o
[1006/2496] Compiling C object drivers/libtmp_rte_net_cxgbe.a.p/net_cxgbe_cxgbe_main.c.o
[1007/2496] Compiling C object drivers/libtmp_rte_net_cxgbe.a.p/net_cxgbe_cxgbe_filter.c.o
[1008/2496] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_80003es2lan.c.o
[1009/2496] Compiling C object drivers/libtmp_rte_net_dpaa.a.p/net_dpaa_dpaa_ethdev.c.o
[1010/2496] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_82543.c.o
[1011/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_mc_dpni.c.o
[1012/2496] Compiling C object drivers/libtmp_rte_net_cpfl.a.p/net_cpfl_cpfl_ethdev.c.o
[1013/2496] Compiling C object drivers/libtmp_rte_net_cxgbe.a.p/net_cxgbe_sge.c.o
[1014/2496] Generating ethdev.sym_chk with a custom command (wrapped by meson to capture output)
FAILED: lib/ethdev.sym_chk
/usr/bin/meson --internal exe --capture lib/ethdev.sym_chk -- /home/zhoumin/gh_dpdk/buildtools/check-symbols.sh /home/zhoumin/gh_dpdk/lib/ethdev/version.map lib/librte_ethdev.a
Found badly formatted maps:
rte_eth_fp_ops; # MSVC_NO_EXPORT
[1015/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_ethdev.c.o
[1016/2496] Compiling C object drivers/libtmp_rte_net_cxgbe.a.p/net_cxgbe_base_t4_hw.c.o
[1017/2496] Generating rte_net_cnxk.pmd.c with a custom command
[1018/2496] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_hwrm.c.o
[1019/2496] Compiling C object drivers/libtmp_rte_net_bond.a.p/net_bonding_rte_eth_bond_pmd.c.o
[1020/2496] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_elink.c.o
[1021/2496] Compiling C object drivers/libtmp_rte_net_dpaa.a.p/net_dpaa_dpaa_rxtx.c.o
[1022/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_flow.c.o
[1023/2496] Generating vhost.sym_chk with a custom command (wrapped by meson to capture output)
[1024/2496] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_rxtx.c.o
[1025/2496] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[1026/2496] 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:[~2024-03-12  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1710229908-31704-4-git-send-email-roretzla@linux.microsoft.com>
2024-03-12  7:29 ` qemudev [this message]
2024-03-12  7:53 ` |SUCCESS| pw138199 " checkpatch
2024-03-12  8:22 ` |FAILURE| " 0-day Robot
2024-03-12  9:41 ` |FAILURE| pw138201-138199 [PATCH] [3/3] " 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=202403120729.42C7T4m72931604@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=roretzla@linux.microsoft.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).