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| pw143652-143654 [PATCH 3/3] examples/ptpclient: add frequency adjustment support
Date: Thu, 5 Sep 2024 18:06:22 +0800	[thread overview]
Message-ID: <202409051006.485A6Mmd1728589@localhost.localdomain> (raw)
In-Reply-To: <20240905100839.861860-4-mingjinx.ye@intel.com>

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

_ninja build failure_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Thu,  5 Sep 2024 10:08:37 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 523fd7b3adfdf5a87651e8ca33bc69223b3211d5

143652-143654 --> 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/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
rte_eth_timesync_adjust_freq is not flagged as experimental
but is listed in version map
Please add __rte_experimental to the definition of rte_eth_timesync_adjust_freq
rte_eth_timesync_read_time is flagged as experimental
but is not listed in version map
Please add rte_eth_timesync_read_time to the version map
[1142/2530] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_res.c.o
[1143/2530] Generating rte_net_cxgbe.pmd.c with a custom command
[1144/2530] Compiling C object drivers/net/fm10k/base/libfm10k_base.a.p/fm10k_api.c.o
[1145/2530] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_base_vnic_dev.c.o
[1146/2530] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe.c.o
[1147/2530] Generating rte_net_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1148/2530] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_eal.c.o
[1149/2530] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_flow.c.o
[1150/2530] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_intr.c.o
[1151/2530] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_rxtx.c.o
[1152/2530] Generating symbol file drivers/librte_bus_pci.so.25.0.p/librte_bus_pci.so.25.0.symbols
[1153/2530] Compiling C object drivers/libtmp_rte_net_ena.a.p/net_ena_ena_ethdev.c.o
[1154/2530] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_igb_rxtx.c.o
[1155/2530] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_args.c.o
[1156/2530] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_igb_ethdev.c.o
[1157/2530] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_ethdev.c.o
[1158/2530] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_flow.c.o
[1159/2530] Generating rte_net_dpaa.pmd.c with a custom command
[1160/2530] Generating symbol file drivers/librte_bus_ifpga.so.25.0.p/librte_bus_ifpga.so.25.0.symbols
[1161/2530] Generating symbol file lib/librte_rcu.so.25.0.p/librte_rcu.so.25.0.symbols
[1162/2530] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_ether.c.o
[1163/2530] Generating symbol file lib/librte_mempool.so.25.0.p/librte_mempool.so.25.0.symbols
[1164/2530] Generating rte_net_bond.sym_chk with a custom command (wrapped by meson to capture output)
[1165/2530] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_rxtx.c.o
[1166/2530] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_rxtx.c.o
[1167/2530] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_fm_flow.c.o
[1168/2530] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_main.c.o
[1169/2530] Generating vhost.sym_chk with a custom command (wrapped by meson to capture output)
[1170/2530] Generating rte_net_bnxt.pmd.c with a custom command
[1171/2530] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_ops.c.o
[1172/2530] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[1173/2530] Compiling C object drivers/libtmp_rte_crypto_octeontx.a.p/crypto_octeontx_otx_cryptodev_ops.c.o
[1174/2530] 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-09-05 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240905100839.861860-4-mingjinx.ye@intel.com>
2024-09-05 10:06 ` qemudev [this message]
2024-09-05 10:33 ` |WARNING| pw143654 " 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=202409051006.485A6Mmd1728589@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).