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: [dpdk-test-report] |FAILURE| pw78677 [PATCH] [v2] regex/mlx5: add dynamic memory registration to datapath
Date: Thu, 24 Sep 2020 08:26:44 -0400 (EDT)	[thread overview]
Message-ID: <20200924122644.ACEFCA600@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/78677

_build patch failure_

Submitter: Yuval Avnery <yuvalav@nvidia.com>
Date: Thursday, September 24 2020 11:55:45 
Applied on: CommitID:f0f5d844d138a1d6564ffe4eb0c56bf41a7cf7c3
Apply patch set 78677 failed:

[1/396] Linking static target drivers/libtmp_rte_pmd_dpaa2_event.a.
[2/396] Linking static target drivers/libtmp_rte_pmd_octeontx_crypto.a.
[3/396] Linking static target drivers/libtmp_rte_pmd_octeontx2_crypto.a.
[4/396] Linking static target drivers/libtmp_rte_pmd_mlx5.a.
[5/396] Linking static target drivers/libtmp_rte_pmd_qat.a.
[6/396] Linking static target drivers/libtmp_rte_pmd_dpaa_event.a.
[7/396] Generating rte_pmd_dpaa_event.pmd.c with a custom command.
[8/396] Generating rte_pmd_octeontx2_event_mingw with a custom command.
[9/396] Generating rte_pmd_octeontx2_event_def with a custom command.
[10/396] Linking target drivers/librte_pmd_crypto_scheduler.so.21.0.
[11/396] Generating rte_pmd_dpaa2_event.pmd.c with a custom command.
[12/396] Generating rte_pmd_octeontx2_crypto.pmd.c with a custom command.
[13/396] Linking target drivers/librte_pmd_ifc.so.21.0.
[14/396] Linking target drivers/librte_pmd_mlx5_regex.so.21.0.
FAILED: drivers/librte_pmd_mlx5_regex.so.21.0 
cc  -o drivers/librte_pmd_mlx5_regex.so.21.0 'drivers/a715181@@rte_pmd_mlx5_regex@sha/meson-generated_.._rte_pmd_mlx5_regex.pmd.c.o' 'drivers/a715181@@tmp_rte_pmd_mlx5_regex@sta/regex_mlx5_mlx5_regex.c.o' 'drivers/a715181@@tmp_rte_pmd_mlx5_regex@sta/regex_mlx5_mlx5_rxp.c.o' 'drivers/a715181@@tmp_rte_pmd_mlx5_regex@sta/regex_mlx5_mlx5_regex_devx.c.o' 'drivers/a715181@@tmp_rte_pmd_mlx5_regex@sta/regex_mlx5_mlx5_regex_control.c.o' 'drivers/a715181@@tmp_rte_pmd_mlx5_regex@sta/regex_mlx5_mlx5_regex_fastpath.c.o' -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,librte_pmd_mlx5_regex.so.21 -Wl,--no-as-needed -pthread -lm -ldl -lnuma lib/librte_ethdev.so.21.0 lib/librte_eal.so.21.0 lib/librte_kvargs.so.21.0 lib/librte_telemetry.so.21.0 lib/librte_net.so.21.0 lib/librte_mbuf.so.21.0 lib/librte_mempool.so.21.0 lib/librte_ring.so.21.0 lib/librte_meter.so.21.0 drivers/librte_common_mlx5.so.21.0 lib/librte_hash.so.21.0 lib/librte_pci.so.21.0 drivers/librte_bus_pci.so.21.0 lib/librte_regexdev.so.21.0 -Wl,--version-script=/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/drivers/regex/mlx5/rte_pmd_mlx5_regex_version.map -lmlx5 -libverbs -Wl,--end-group '-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
drivers/a715181@@tmp_rte_pmd_mlx5_regex@sta/regex_mlx5_mlx5_regex.c.o: In function `mlx5_regex_pci_probe':
mlx5_regex.c:(.text+0x4b5): undefined reference to `mlx5_os_set_reg_mr_cb'
collect2: error: ld returned 1 exit status
[15/396] Linking target drivers/librte_pmd_mlx5_vdpa.so.21.0.
[16/396] Compiling C object 'drivers/a715181@@rte_pmd_dpaa_event@sha/meson-generated_.._rte_pmd_dpaa_event.pmd.c.o'.
[17/396] Compiling C object 'drivers/a715181@@rte_pmd_dpaa_event@sta/meson-generated_.._rte_pmd_dpaa_event.pmd.c.o'.
[18/396] Generating rte_pmd_octeontx_crypto.pmd.c with a custom command.
[19/396] Compiling C object 'drivers/a715181@@rte_pmd_dpaa2_event@sta/meson-generated_.._rte_pmd_dpaa2_event.pmd.c.o'.
[20/396] Generating rte_pmd_qat.pmd.c with a custom command.
[21/396] Compiling C object 'drivers/a715181@@rte_pmd_dpaa2_event@sha/meson-generated_.._rte_pmd_dpaa2_event.pmd.c.o'.
[22/396] Compiling C object 'drivers/a715181@@rte_pmd_octeontx2_crypto@sta/meson-generated_.._rte_pmd_octeontx2_crypto.pmd.c.o'.
[23/396] Generating rte_pmd_opdl_event_mingw with a custom command.
[24/396] Generating rte_pmd_opdl_event_def with a custom command.
[25/396] Generating rte_pmd_mlx5.pmd.c with a custom command.
[26/396] Compiling C object 'drivers/a715181@@tmp_rte_pmd_opdl_event@sta/event_opdl_opdl_evdev.c.o'.
[27/396] Compiling C object 'drivers/a715181@@tmp_rte_pmd_opdl_event@sta/event_opdl_opdl_evdev_init.c.o'.
[28/396] Compiling C object 'drivers/a715181@@tmp_rte_pmd_octeontx2_event@sta/event_octeontx2_otx2_tim_evdev.c.o'.
[29/396] Compiling C object 'drivers/a715181@@tmp_rte_pmd_opdl_event@sta/event_opdl_opdl_test.c.o'.
[30/396] Compiling C object 'drivers/a715181@@tmp_rte_pmd_octeontx2_event@sta/event_octeontx2_otx2_tim_worker.c.o'.
[31/396] Compiling C object 'drivers/a715181@@tmp_rte_pmd_opdl_event@sta/event_opdl_opdl_ring.c.o'.
ninja: build stopped: subcommand failed.

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2020-09-24 12:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200924122644.ACEFCA600@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).