From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
John Miller <john.miller@atomicrules.com>
Subject: |FAILURE| pw119167-119180 [PATCH] [14/14] baseband/meson.build:
Date: Wed, 26 Oct 2022 21:08:55 +0000 (UTC) [thread overview]
Message-ID: <20221026210855.4CDE660091@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3209 bytes --]
Test-Label: iol-aarch64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/119180
_Testing issues_
Submitter: John Miller <john.miller@atomicrules.com>
Date: Wednesday, October 26 2022 19:46:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:011c617ca20858ce0ad20625e9d3e4c3d6252047
119167-119180 --> testing fail
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| Ubuntu 20.04 ARM GCC Native | FAIL |
+-------------------------------+----------------+
| Ubuntu 20.04 ARM Clang Native | FAIL |
+-------------------------------+----------------+
==== 20 line log output for Ubuntu 20.04 ARM Clang Native (dpdk_unit_test): ====
[3143/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn10k_deq_112_127_tmo_seg.c.o
[3144/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn10k_deq_96_111_ca_tmo_seg.c.o
[3145/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn10k_deq_112_127_ca_tmo_seg.c.o
[3146/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_0_15.c.o
[3147/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_32_47.c.o
[3148/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_16_31.c.o
[3149/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_48_63.c.o
[3150/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_64_79.c.o
[3151/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_96_111.c.o
[3152/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_80_95.c.o
[3153/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_112_127.c.o
[3154/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_32_47_seg.c.o
[3155/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_16_31_seg.c.o
[3156/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_0_15_seg.c.o
[3157/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_48_63_seg.c.o
[3158/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_64_79_seg.c.o
[3159/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_96_111_seg.c.o
[3160/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_80_95_seg.c.o
[3161/3519] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_112_127_seg.c.o
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/24209/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-10-26 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 21:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-26 20:44 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=20221026210855.4CDE660091@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=john.miller@atomicrules.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).