From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>,
Feifei Wang <wff_light@vip.163.com>
Subject: |FAILURE| pw156292-156308 [PATCH] [V6,17/17] drivers/net: add hinic3
Date: Wed, 10 Sep 2025 00:01:35 -0700 (PDT) [thread overview]
Message-ID: <68c1224f.630a0220.34b765.6d9bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250830124332.5351-18-wff_light@vip.163.com>
Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/156308
_Testing issues_
Submitter: Feifei Wang <wff_light@vip.163.com>
Date: Saturday, August 30 2025 12:43:21
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:027d974ef56f7312133934422ea0f8971c224603
156292-156308 --> testing issues
Upstream job id: Generic-VM-DPDK-Compile-Meson#38225
Test environment and result as below:
+--------------+--------------------+
| Environment | dpdk_meson_compile |
+==============+====================+
| Ubuntu 20.04 | FAIL |
+--------------+--------------------+
| FreeBSD 14.2 | PASS |
+--------------+--------------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_meson_compile): ====
[1850/3560] Linking target drivers/librte_net_hns3.so.26.0
[1851/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_ixgbe_ethdev.c.o
[1852/3560] Linking target drivers/librte_net_fm10k.so.26.0
[1853/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_ixgbe_flow.c.o
[1854/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_ixgbe_pf.c.o
[1855/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_ixgbe_rxtx.c.o
[1856/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_ixgbe_tm.c.o
[1857/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_ixgbe_vf_representor.c.o
[1858/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_ixgbe_ipsec.c.o
[1859/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_rte_pmd_ixgbe.c.o
[1860/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_ixgbe_rxtx_vec_common.c.o
[1861/3560] Compiling C object drivers/libtmp_rte_net_ixgbe.a.p/net_intel_ixgbe_ixgbe_rxtx_vec_sse.c.o
[1862/3560] Generating rte_net_idpf.pmd.c with a custom command
[1863/3560] Generating rte_net_e1000.sym_chk with a custom command (wrapped by meson to capture output)
[1864/3560] Generating rte_net_ice.pmd.c with a custom command
[1865/3560] Generating rte_net_iavf.sym_chk with a custom command (wrapped by meson to capture output)
[1866/3560] Generating rte_net_i40e.sym_chk with a custom command (wrapped by meson to capture output)
[1867/3560] Generating rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
[1868/3560] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04
Kernel: 4.19
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33994/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-09-10 7:01 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250830124332.5351-18-wff_light@vip.163.com>
2025-08-30 12:17 ` |SUCCESS| pw156292-156308 [V6 17/17] drivers/net: add hinic3 PMD build and doc files qemudev
2025-08-30 12:22 ` qemudev
2025-08-30 12:49 ` |SUCCESS| pw156308 " checkpatch
2025-08-30 13:45 ` |FAILURE| " 0-day Robot
2025-09-10 6:51 ` |FAILURE| pw156292-156308 [PATCH] [V6,17/17] drivers/net: add hinic3 dpdklab
2025-09-10 7:01 ` dpdklab [this message]
2025-09-10 7:08 ` |SUCCESS| " dpdklab
2025-09-10 7:25 ` dpdklab
2025-09-10 8:33 ` dpdklab
2025-09-10 8:55 ` dpdklab
2025-09-10 9:19 ` |PENDING| " dpdklab
2025-09-10 9:25 ` |WARNING| " dpdklab
2025-09-10 9:25 ` dpdklab
2025-09-10 9:26 ` dpdklab
2025-09-10 9:27 ` dpdklab
2025-09-10 9:34 ` |FAILURE| " dpdklab
2025-09-10 9:34 ` dpdklab
2025-09-10 9:35 ` |WARNING| " dpdklab
2025-09-10 9:35 ` |FAILURE| " dpdklab
2025-09-10 9:39 ` dpdklab
2025-09-10 9:46 ` dpdklab
2025-09-10 9:47 ` dpdklab
2025-09-10 9:48 ` dpdklab
2025-09-10 9:48 ` dpdklab
2025-09-10 9:48 ` dpdklab
2025-09-10 9:51 ` dpdklab
2025-09-10 9:52 ` dpdklab
2025-09-10 9:56 ` dpdklab
2025-09-10 10:00 ` |WARNING| " dpdklab
2025-09-10 10:02 ` |FAILURE| " dpdklab
2025-09-10 10:03 ` dpdklab
2025-09-10 10:26 ` dpdklab
2025-09-10 11:17 ` |WARNING| " dpdklab
2025-09-10 11:21 ` |FAILURE| " dpdklab
2025-09-10 11:39 ` |WARNING| " dpdklab
2025-09-10 11:46 ` |FAILURE| " dpdklab
2025-09-10 12:29 ` |SUCCESS| " dpdklab
2025-09-10 12:40 ` |FAILURE| " dpdklab
2025-09-10 12:58 ` |SUCCESS| " dpdklab
2025-09-10 13:11 ` |FAILURE| " dpdklab
2025-09-10 15:03 ` dpdklab
2025-09-10 15:30 ` |WARNING| " 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=68c1224f.630a0220.34b765.6d9bSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--cc=test-report@dpdk.org \
--cc=wff_light@vip.163.com \
/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).