automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |FAILURE| pw123499-123500 [PATCH] [2/2] test/mempool: add zero-copy API's
Date: Thu,  9 Feb 2023 01:39:47 -0500 (EST)	[thread overview]
Message-ID: <20230209063947.CD5173ECAD@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 4688 bytes --]

Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/123499

_build patch failure_

Submitter: Kamalakshitha Aligeri <kamalakshitha.aligeri@arm.com>
Date: Thursday, February 09 2023 06:25:01 
Applied on: CommitID:a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00
Apply patch set 123499-123500 failed:

[1/1502] Linking static target drivers/libtmp_rte_net_ixgbe.a
[2/1502] Linking static target drivers/libtmp_rte_net_liquidio.a
[3/1502] Linking static target drivers/libtmp_rte_net_memif.a
[4/1502] Linking target drivers/librte_net_ice.so.23.1
[5/1502] Linking target drivers/librte_net_i40e.so.23.1
FAILED: drivers/librte_net_i40e.so.23.1 
cc  -o drivers/librte_net_i40e.so.23.1 drivers/librte_net_i40e.so.23.1.p/meson-generated_.._rte_net_i40e.pmd.c.o drivers/net/i40e/base/libi40e_base.a.p/i40e_adminq.c.o drivers/net/i40e/base/libi40e_base.a.p/i40e_common.c.o drivers/net/i40e/base/libi40e_base.a.p/i40e_dcb.c.o drivers/net/i40e/base/libi40e_base.a.p/i40e_diag.c.o drivers/net/i40e/base/libi40e_base.a.p/i40e_hmc.c.o drivers/net/i40e/base/libi40e_base.a.p/i40e_lan_hmc.c.o drivers/net/i40e/base/libi40e_base.a.p/i40e_nvm.c.o drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_ethdev.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_rxtx.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_pf.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_fdir.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_flow.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_tm.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_hash.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_vf_representor.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_rte_pmd_i40e.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_rxtx_vec_sse.c.o drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_rxtx_vec_avx2.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,librte_net_i40e.so.23 -Wl,--no-as-needed -pthread -lm -ldl -lnuma -lfdt '-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/' -Wl,-rpath-link,/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/build/lib -Wl,-rpath-link,/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/build/drivers lib/librte_ethdev.so.23.1 lib/librte_eal.so.23.1 lib/librte_kvargs.so.23.1 lib/librte_telemetry.so.23.1 lib/librte_net.so.23.1 lib/librte_mbuf.so.23.1 lib/librte_mempool.so.23.1 lib/librte_ring.so.23.1 lib/librte_meter.so.23.1 drivers/librte_bus_pci.so.23.1 lib/librte_pci.so.23.1 drivers/librte_bus_vdev.so.23.1 lib/librte_hash.so.23.1 lib/librte_rcu.so.23.1 -Wl,--end-group -Wl,--version-script=/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/drivers/net/i40e/version.map
drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_rxtx_vec_sse.c.o: In function `i40e_xmit_fixed_burst_vec':
i40e_rxtx_vec_sse.c:(.text+0x3b33): undefined reference to `rte_mempool_cache_zc_put_bulk'
drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_rxtx_vec_avx2.c.o: In function `i40e_xmit_fixed_burst_vec_avx2':
i40e_rxtx_vec_avx2.c:(.text+0xc9b): undefined reference to `rte_mempool_cache_zc_put_bulk'
collect2: error: ld returned 1 exit status
[6/1502] Compiling C object drivers/libtmp_rte_net_mlx4.a.p/net_mlx4_mlx4_glue.c.o
[7/1502] Generating rte_net_memif.pmd.c with a custom command
[8/1502] Generating rte_net_liquidio.pmd.c with a custom command
[9/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_dv.c.o
[10/1502] Compiling C object drivers/libtmp_rte_net_mlx4.a.p/net_mlx4_mlx4_utils.c.o
[11/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_mac.c.o
[12/1502] Compiling C object drivers/libtmp_rte_net_mlx4.a.p/net_mlx4_mlx4_txq.c.o
[13/1502] Generating rte_net_ixgbe.pmd.c with a custom command
[14/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rss.c.o
[15/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_ethdev.c.o
[16/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_flex.c.o
[17/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5.c.o
[18/1502] Compiling C object drivers/libtmp_rte_net_mlx4.a.p/net_mlx4_mlx4_rxtx.c.o
[19/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_meter.c.o
[20/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_aso.c.o
[21/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rx.c.o
[22/1502] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow.c.o
ninja: build stopped: subcommand failed.

https://lab.dpdk.org/results/dashboard/patchsets/25305/

UNH-IOL DPDK Community Lab

             reply	other threads:[~2023-02-09  6:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  6:39 dpdklab [this message]
     [not found] <20230209062501.142828-2-kamalakshitha.aligeri@arm.com>
2023-02-09  6:14 ` |FAILURE| pw123499-123500 [PATCH 2/2] " 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=20230209063947.CD5173ECAD@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    /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).