automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Sivaprasad Tummala <sivaprasad.tummala@amd.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw146334-146337 [PATCH v6 5/5] maintainers: update for drivers/power
Date: Mon, 21 Oct 2024 11:05:57 +0800	[thread overview]
Message-ID: <202410210305.49L35vJm221899@localhost.localdomain> (raw)
In-Reply-To: <20241020092233.2906612-6-sivaprasad.tummala@amd.com>

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

_ninja build failure_

Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Sun, 20 Oct 2024 09:22:28 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e609858b480ca0d646e5f05f2c7fd6bbf35a4140

146334-146337 --> 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/librte_power.so.25.0
cc -o lib/librte_power.so.25.0 lib/librte_power.a.p/power_power_common.c.o lib/librte_power.a.p/power_rte_power.c.o lib/librte_power.a.p/power_rte_power_uncore.c.o lib/librte_power.a.p/power_rte_power_pmd_mgmt.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,librte_power.so.25 -Wl,--no-as-needed -pthread -lm -ldl -lnuma -lfdt '-Wl,-rpath,$ORIGIN/' -Wl,-rpath-link,/home/zhoumin/gh_dpdk/build/lib lib/librte_eal.so.25.0 lib/librte_kvargs.so.25.0 lib/librte_log.so.25.0 lib/librte_telemetry.so.25.0 lib/librte_timer.so.25.0 lib/librte_ethdev.so.25.0 lib/librte_net.so.25.0 lib/librte_mbuf.so.25.0 lib/librte_mempool.so.25.0 lib/librte_ring.so.25.0 lib/librte_meter.so.25.0 -Wl,--end-group -Wl,--version-script=/home/zhoumin/gh_dpdk/lib/power/version.map
/usr/bin/ld: lib/librte_power.a.p/power_rte_power_uncore.c.o: in function `rte_power_get_uncore_freq':
rte_power_uncore.c:(.text+0x1e0): undefined reference to `RTE_ASSERT'
/usr/bin/ld: lib/librte_power.a.p/power_rte_power_uncore.c.o: in function `rte_power_set_uncore_freq':
rte_power_uncore.c:(.text+0x234): undefined reference to `RTE_ASSERT'
/usr/bin/ld: lib/librte_power.a.p/power_rte_power_uncore.c.o: in function `rte_power_uncore_freq_max':
rte_power_uncore.c:(.text+0x288): undefined reference to `RTE_ASSERT'
/usr/bin/ld: lib/librte_power.a.p/power_rte_power_uncore.c.o: in function `rte_power_uncore_freq_min':
rte_power_uncore.c:(.text+0x2d8): undefined reference to `RTE_ASSERT'
/usr/bin/ld: lib/librte_power.a.p/power_rte_power_uncore.c.o: in function `rte_power_uncore_get_num_freqs':
rte_power_uncore.c:(.text+0x328): undefined reference to `RTE_ASSERT'
/usr/bin/ld: lib/librte_power.a.p/power_rte_power_uncore.c.o:rte_power_uncore.c:(.text+0x36c): more undefined references to `RTE_ASSERT' follow
collect2: error: ld returned 1 exit status
[1295/2577] Linking target lib/librte_lpm.so.25.0
[1296/2577] Generating symbol file lib/librte_security.so.25.0.p/librte_security.so.25.0.symbols
[1297/2577] Linking target lib/librte_fib.so.25.0
[1298/2577] Linking target lib/librte_member.so.25.0
[1299/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_fdir.c.o
[1300/2577] Linking target lib/librte_vhost.so.25.0
[1301/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_nvm.c.o
[1302/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_imem.c.o
[1303/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_parser.c.o
[1304/2577] Generating symbol file drivers/librte_common_cpt.so.25.0.p/librte_common_cpt.so.25.0.symbols
[1305/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_acl_ctrl.c.o
[1306/2577] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_ethdev.c.o
[1307/2577] Generating rte_net_failsafe.pmd.c with a custom command
[1308/2577] Generating rte_net_fm10k.pmd.c with a custom command
[1309/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_bst_tcam.c.o
[1310/2577] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_vchnl.c.o
[1311/2577] Generating symbol file lib/librte_metrics.so.25.0.p/librte_metrics.so.25.0.symbols
[1312/2577] Generating symbol file lib/librte_ip_frag.so.25.0.p/librte_ip_frag.so.25.0.symbols
[1313/2577] Generating symbol file lib/librte_gso.so.25.0.p/librte_gso.so.25.0.symbols
[1314/2577] Generating symbol file lib/librte_pcapng.so.25.0.p/librte_pcapng.so.25.0.symbols
[1315/2577] Generating rte_net_hinic.pmd.c with a custom command
[1316/2577] Generating rte_net_bnxt.pmd.c with a custom command
[1317/2577] Generating symbol file lib/librte_bpf.so.25.0.p/librte_bpf.so.25.0.symbols
[1318/2577] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[1319/2577] Generating symbol file lib/librte_eventdev.so.25.0.p/librte_eventdev.so.25.0.symbols
[1320/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_flex_pipe.c.o
[1321/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_common.c.o
[1322/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_sched.c.o
[1323/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_ptp_hw.c.o
[1324/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_switch.c.o
[1325/2577] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_rxtx.c.o
[1326/2577] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_flow.c.o
[1327/2577] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------


  parent reply	other threads:[~2024-10-22  8:22 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241020092233.2906612-6-sivaprasad.tummala@amd.com>
2024-10-20  9:25 ` |SUCCESS| pw146337 " checkpatch
2024-10-20 10:24 ` |FAILURE| " 0-day Robot
2024-10-20 10:31 ` |SUCCESS| pw146334-146337 [PATCH] [v6,5/5] maintainers: update for d dpdklab
2024-10-20 10:39 ` dpdklab
2024-10-20 10:44 ` dpdklab
2024-10-20 10:44 ` dpdklab
2024-10-20 10:47 ` dpdklab
2024-10-20 10:47 ` dpdklab
2024-10-20 10:48 ` dpdklab
2024-10-20 10:51 ` dpdklab
2024-10-20 10:56 ` |PENDING| " dpdklab
2024-10-20 10:58 ` |SUCCESS| " dpdklab
2024-10-20 11:22 ` |FAILURE| " dpdklab
2024-10-20 11:24 ` |SUCCESS| " dpdklab
2024-10-20 11:42 ` |FAILURE| " dpdklab
2024-10-20 11:47 ` |SUCCESS| " dpdklab
2024-10-20 14:49 ` |PENDING| " dpdklab
2024-10-20 15:39 ` |FAILURE| " dpdklab
2024-10-20 15:50 ` dpdklab
2024-10-20 15:52 ` dpdklab
2024-10-20 15:53 ` dpdklab
2024-10-20 15:54 ` dpdklab
2024-10-20 15:57 ` |WARNING| " dpdklab
2024-10-20 16:06 ` |FAILURE| " dpdklab
2024-10-20 16:12 ` dpdklab
2024-10-20 16:14 ` dpdklab
2024-10-20 16:50 ` dpdklab
2024-10-20 16:53 ` dpdklab
2024-10-20 16:58 ` dpdklab
2024-10-20 17:01 ` dpdklab
2024-10-20 17:07 ` dpdklab
2024-10-20 17:29 ` dpdklab
2024-10-20 17:33 ` |WARNING| " dpdklab
2024-10-20 18:10 ` |FAILURE| " dpdklab
2024-10-20 22:36 ` |WARNING| " dpdklab
2024-10-21  3:05 ` qemudev [this message]
2024-10-22  3:14 ` |FAILURE| pw146334-146337 [PATCH v6 5/5] maintainers: update for drivers/power qemudev

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=202410210305.49L35vJm221899@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=sivaprasad.tummala@amd.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).