automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw98856 [PATCH] [v2] examples/ipsec-secgw: add support for event vector
Date: Wed, 15 Sep 2021 18:38:10 -0400 (EDT)	[thread overview]
Message-ID: <20210915223810.A31E24B0@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-aarch64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/98856

_Testing issues_

Submitter: Srujana Challa <schalla@marvell.com>
Date: Tuesday, September 14 2021 13:14:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:af167bcf174b59fa4776297e628a94143cf6a330

98856 --> testing fail

Test environment and result as below:

+------------------------------------+--------------------+
|            Environment             | dpdk_meson_compile |
+====================================+====================+
| 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;
|              ^
[2695/2850] Compiling C object examples/dpdk-ip_pipeline.p/ip_pipeline_tmgr.c.o
[2696/2850] Compiling C object examples/dpdk-ip_pipeline.p/ip_pipeline_parser.c.o
[2697/2850] Compiling C object examples/dpdk-ip_pipeline.p/ip_pipeline_pipeline.c.o
[2698/2850] Compiling C object examples/dpdk-l2fwd.p/l2fwd_main.c.o
[2699/2850] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_flow.c.o
[2700/2850] Compiling C object examples/dpdk-ip_reassembly.p/ip_reassembly_main.c.o
[2701/2850] Compiling C object examples/dpdk-ipsec-secgw.p/ipsec-secgw_ipsec.c.o
[2702/2850] Compiling C object examples/dpdk-ip_pipeline.p/ip_pipeline_thread.c.o
[2703/2850] Compiling C object examples/dpdk-ip_pipeline.p/ip_pipeline_cli.c.o
[2704/2850] Compiling C object app/test/dpdk-test.p/test_ring_perf.c.o
[2705/2850] Compiling C object app/test/dpdk-test.p/test_trace_perf.c.o
[2706/2850] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_deq_tmo.c.o
[2707/2850] Compiling C object app/test/dpdk-test.p/test_ring.c.o
[2708/2850] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_tx_enq.c.o
[2709/2850] Compiling C object drivers/libtmp_rte_event_octeontx2.a.p/event_octeontx2_otx2_worker.c.o
[2710/2850] Compiling C object drivers/libtmp_rte_event_octeontx2.a.p/event_octeontx2_otx2_worker_dual.c.o
[2711/2850] 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 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/18735/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

                 reply	other threads:[~2021-09-15 22:38 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=20210915223810.A31E24B0@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).