From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Shijith Thotton <sthotton@marvell.com>
Subject: [dpdk-test-report] |FAILURE| pw97979 [PATCH] [v2] examples/l3fwd: add changes to use event vector
Date: Sat, 4 Sep 2021 20:38:45 -0400 (EDT) [thread overview]
Message-ID: <20210905003845.07E4488E6A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2728 bytes --]
Test-Label: iol-aarch64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/97979
_Testing issues_
Submitter: Shijith Thotton <sthotton@marvell.com>
Date: Saturday, September 04 2021 07:46:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:eeedef704c11bd74c367d62838700bdb8e5b573f
97979 --> testing fail
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM cross-compilation | FAIL |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM | FAIL |
+------------------------------------+--------------------+
==== 20 line log output for Ubuntu 20.04 ARM (dpdk_meson_compile): ====
231 | eth_q_conf.vector_sz = evt_rsrc->vector_size;
| ^
../examples/l3fwd/l3fwd_event_internal_port.c:232:15: error: ‘struct rte_event_eth_rx_adapter_queue_conf’ has no member named ‘vector_timeout_ns’
232 | eth_q_conf.vector_timeout_ns =
| ^
../examples/l3fwd/l3fwd_event_internal_port.c:234:15: error: ‘struct rte_event_eth_rx_adapter_queue_conf’ has no member named ‘vector_mp’
234 | eth_q_conf.vector_mp =
| ^
[2738/3070] Generating rte_baseband_fpga_5gnr_fec.sym_chk with a custom command (wrapped by meson to capture output)
[2739/3070] Compiling C object examples/dpdk-l3fwd.p/l3fwd_l3fwd_event.c.o
[2740/3070] Compiling C object examples/dpdk-l3fwd.p/l3fwd_l3fwd_event_generic.c.o
[2741/3070] Compiling C object examples/dpdk-l3fwd.p/l3fwd_main.c.o
[2742/3070] Compiling C object examples/dpdk-l3fwd.p/l3fwd_l3fwd_lpm.c.o
[2743/3070] Compiling C object examples/dpdk-l3fwd.p/l3fwd_l3fwd_em.c.o
[2744/3070] Compiling C object examples/dpdk-l3fwd.p/l3fwd_l3fwd_fib.c.o
[2745/3070] Generating rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
[2746/3070] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[2747/3070] Generating eal.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
[1] Error running command.
==== 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
Ubuntu 20.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18550/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-09-05 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 0:38 dpdklab [this message]
2021-09-05 9:11 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=20210905003845.07E4488E6A@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=sthotton@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).