From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw82362 [PATCH] net/mlx5: use C11 atomics in packet scheduling
Date: Tue, 27 Oct 2020 15:40:18 -0400 (EDT) [thread overview]
Message-ID: <20201027194018.A6FB288E65@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3620 bytes --]
Test-Label: Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/82362
_build patch failure_
Submitter: Slava Ovsiienko <viacheslavo@nvidia.com>
Date: Tuesday, October 27 2020 19:03:19
Applied on: CommitID:8c287f8ed6d549428d9979316f7179bf0b4e0f90
Apply patch set 82362 failed:
[1/23] Linking static target drivers/libtmp_rte_event_octeontx2.a.
[2/23] Linking target drivers/librte_net_mlx5.so.21.0.
FAILED: drivers/librte_net_mlx5.so.21.0
cc -o drivers/librte_net_mlx5.so.21.0 'drivers/a715181@@rte_net_mlx5@sha/meson-generated_.._rte_net_mlx5.pmd.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_ethdev.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_meter.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_dv.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_verbs.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_mac.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_mr.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rss.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rxmode.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rxq.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rxtx.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_stats.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_trigger.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_txq.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_txpp.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_vlan.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_utils.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_devx.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rxtx_vec.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_socket.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_os.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_ethdev_os.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_verbs.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_mp_os.c.o' 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_vlan_os.c.o' -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,librte_net_mlx5.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_bus_pci.so.21.0 lib/librte_pci.so.21.0 drivers/librte_bus_vdev.so.21.0 lib/librte_hash.so.21.0 drivers/librte_common_mlx5.so.21.0 -Wl,--version-script=/home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/drivers/net/mlx5/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_net_mlx5@sta/net_mlx5_mlx5_txpp.c.o: In function `mlx5_txpp_read_clock':
mlx5_txpp.c:(.text+0x6f2): undefined reference to `__atomic_compare_exchange_16'
collect2: error: ld returned 1 exit status
[3/23] Generating rte_event_octeontx2.pmd.c with a custom command.
ninja: build stopped: subcommand failed.
https://lab.dpdk.org/results/dashboard/patchsets/14077/
UNH-IOL DPDK Community Lab
reply other threads:[~2020-10-27 19:40 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=20201027194018.A6FB288E65@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).