From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Srujana Challa <schalla@marvell.com>
Subject: [dpdk-test-report] |FAILURE| pw97354 [PATCH] examples/ipsec-secgw: add support for event vector
Date: Thu, 26 Aug 2021 13:20:20 -0400 (EDT) [thread overview]
Message-ID: <20210826172020.244C889060@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2832 bytes --]
Test-Label: iol-aarch64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/97354
_Testing issues_
Submitter: Srujana Challa <schalla@marvell.com>
Date: Thursday, August 26 2021 10:03:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fdab8f2e17493192d555cd88cf28b06269174326
97354 --> testing fail
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM | FAIL |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM cross-compilation | FAIL |
+------------------------------------+--------------------+
==== 20 line log output for Ubuntu 20.04 ARM cross-compilation (dpdk_meson_compile): ====
847 | queue_conf.vector_mp = vector_pool;
| ^
[2684/2839] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_deq_tmo.c.o
[2685/2839] Compiling C object examples/dpdk-ip_fragmentation.p/ip_fragmentation_main.c.o
[2686/2839] Linking target examples/dpdk-ip_reassembly
[2687/2839] Compiling C object examples/dpdk-ip_pipeline.p/ip_pipeline_pipeline.c.o
[2688/2839] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_esp.c.o
[2689/2839] Compiling C object examples/dpdk-ipv4_multicast.p/ipv4_multicast_main.c.o
[2690/2839] Compiling C object examples/dpdk-l2fwd.p/l2fwd_main.c.o
[2691/2839] Compiling C object examples/dpdk-kni.p/kni_main.c.o
[2692/2839] Compiling C object examples/dpdk-ip_pipeline.p/ip_pipeline_thread.c.o
[2693/2839] Compiling C object examples/dpdk-ip_pipeline.p/ip_pipeline_cli.c.o
[2694/2839] Compiling C object app/test/dpdk-test.p/test_ring_perf.c.o
[2695/2839] Compiling C object app/test/dpdk-test.p/test_trace_perf.c.o
[2696/2839] Compiling C object app/test/dpdk-test.p/test_ring.c.o
[2697/2839] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_tx_enq.c.o
[2698/2839] Compiling C object drivers/libtmp_rte_event_octeontx2.a.p/event_octeontx2_otx2_worker.c.o
[2699/2839] Compiling C object drivers/libtmp_rte_event_octeontx2.a.p/event_octeontx2_otx2_worker_dual.c.o
[2700/2839] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_tx_enq_seg.c.o
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM cross-compilation
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18354/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-08-26 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 17:20 dpdklab [this message]
2021-08-26 17:32 dpdklab
2021-08-26 20:58 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=20210826172020.244C889060@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=schalla@marvell.com \
--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).