From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: [dpdk-test-report] |FAILURE| pw101196-101200 [PATCH] [v4, 5/5] net/mlx5: update modify field action
Date: Thu, 14 Oct 2021 10:44:27 -0400 (EDT) [thread overview]
Message-ID: <20211014144427.4A1CC60524@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3105 bytes --]
Test-Label: iol-aarch64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/101200
_Testing issues_
Submitter: Slava Ovsiienko <viacheslavo@nvidia.com>
Date: Tuesday, October 12 2021 10:49:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e0ae3db0c043cbdc4cc22bb60206f21ec4a82a02
101196-101200 --> testing fail
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM | FAIL |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM cross-compilation | PASS |
+------------------------------------+--------------------+
==== 20 line log output for Ubuntu 20.04 ARM (dpdk_meson_compile): ====
[2115/3122] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_cn10k_rx_vec.c.o
[2116/3122] Generating eal.sym_chk with a custom command (wrapped by meson to capture output)
[2117/3122] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_nompw.c.o
[2118/3122] Generating rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
[2119/3122] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec.c.o
[2120/3122] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_empw.c.o
[2121/3122] Compiling C object drivers/libtmp_rte_crypto_octeontx2.a.p/crypto_octeontx2_otx2_cryptodev_ops.c.o
[2122/3122] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_txpp.c.o
[2123/3122] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[2124/3122] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_cn9k_rx_vec_mseg.c.o
[2125/3122] Compiling C object drivers/libtmp_rte_crypto_octeontx.a.p/crypto_octeontx_otx_cryptodev_ops.c.o
[2126/3122] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_cn9k_tx_vec.c.o
[2127/3122] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_tx.c.o
[2128/3122] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_cn10k_rx_vec_mseg.c.o
[2129/3122] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_cn9k_tx_vec_mseg.c.o
[2130/3122] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_rx.c.o
[2131/3122] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_cn10k_tx_vec.c.o
[2132/3122] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_cn10k_tx_vec_mseg.c.o
ninja: build stopped: subcommand failed.
[1] Error running command.
==== 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/19332/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-10-14 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 14:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-13 1:55 dpdklab
2021-10-12 19:59 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=20211014144427.4A1CC60524@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=viacheslavo@nvidia.com \
/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).