automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>, zhoumin@loongson.cn
Subject: |FAILURE| pw133311 [PATCH v2] eal/unix: allow creating thread with real-time priority
Date: Wed, 25 Oct 2023 22:56:48 +0800	[thread overview]
Message-ID: <202310251456.39PEumUC3346982@localhost.localdomain> (raw)
In-Reply-To: <20231025151352.995318-1-thomas@monjalon.net>

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

_ninja build failure_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Wed, 25 Oct 2023 17:13:14 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 2a0557d1ea21c3f63a212385348c97c414970e81

133311 --> 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_thread_yield is not flagged as experimental
but is listed in version map
Please add __rte_experimental to the definition of rte_thread_yield
[999/2378] Compiling C object drivers/libtmp_rte_net_bond.a.p/net_bonding_rte_eth_bond_pmd.c.o
[1000/2378] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_res.c.o
[1001/2378] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_eal.c.o
[1002/2378] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_phy.c.o
[1003/2378] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_base_vnic_dev.c.o
[1004/2378] Generating rte_net_enetc.pmd.c with a custom command
[1005/2378] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_intr.c.o
[1006/2378] Compiling C object drivers/libtmp_rte_net_ena.a.p/net_ena_base_ena_com.c.o
[1007/2378] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_ich8lan.c.o
[1008/2378] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_vf_representor.c.o
[1009/2378] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_flow.c.o
[1010/2378] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_ether.c.o
[1011/2378] Generating rte_net_enetfec.pmd.c with a custom command
[1012/2378] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_em_rxtx.c.o
[1013/2378] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_args.c.o
[1014/2378] Compiling C object drivers/libtmp_rte_net_dpaa.a.p/net_dpaa_dpaa_rxtx.c.o
[1015/2378] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_ethdev.c.o
[1016/2378] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_flow.c.o
[1017/2378] Generating rte_net_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1018/2378] Generating rte_net_cxgbe.pmd.c with a custom command
[1019/2378] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_rxtx.c.o
[1020/2378] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_fm_flow.c.o
[1021/2378] Generating ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[1022/2378] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_igb_rxtx.c.o
[1023/2378] Compiling C object drivers/libtmp_rte_net_ena.a.p/net_ena_ena_ethdev.c.o
[1024/2378] Generating rte_net_bnx2x.pmd.c with a custom command
[1025/2378] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_main.c.o
[1026/2378] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_igb_ethdev.c.o
[1027/2378] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_rxtx.c.o
[1028/2378] Generating vhost.sym_chk with a custom command (wrapped by meson to capture output)
[1029/2378] Generating rte_net_bnxt.pmd.c with a custom command
[1030/2378] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[1031/2378] 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-10-25 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231025151352.995318-1-thomas@monjalon.net>
2023-10-25 14:56 ` qemudev [this message]
2023-10-25 15:17 ` |WARNING| " checkpatch
2023-10-25 15:40 ` |FAILURE| " 0-day Robot
2023-10-25 15:46 |FAILURE| pw133311 [PATCH] [v2] " 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=202310251456.39PEumUC3346982@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).