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
Subject: [dpdk-test-report] |FAILURE| pw96604-96605 [PATCH] [2/2] net: macro to extract MAC address bytes
Date: Tue,  3 Aug 2021 10:36:34 -0400 (EDT)	[thread overview]
Message-ID: <20210803143634.41A3D89035@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Testing issues_

Submitter: Aman Singh <aman.deep.singh@intel.com>
Date: Tuesday, August 03 2021 09:51:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:31a2db5a177649f4b979e148c89d9f248c0ca97a

96604-96605 --> 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): ====
763 |  }
|  ~
[2558/2839] Compiling C object app/test/dpdk-test.p/test_lpm6.c.o
[2559/2839] Compiling C object app/test/dpdk-test.p/test_malloc.c.o
[2560/2839] Compiling C object app/test/dpdk-test.p/test_mempool_perf.c.o
[2561/2839] Compiling C object app/test/dpdk-test.p/test_lpm_perf.c.o
[2562/2839] Compiling C object app/test/dpdk-test.p/test_lpm.c.o
[2563/2839] Compiling C object app/test/dpdk-test.p/test_member_perf.c.o
[2564/2839] Compiling C object app/test/dpdk-test.p/test_memzone.c.o
[2565/2839] Compiling C object app/test/dpdk-test.p/test_ipsec.c.o
[2566/2839] Compiling C object app/test/dpdk-test.p/test_event_timer_adapter.c.o
[2567/2839] Compiling C object app/test/dpdk-test.p/test_memcpy_perf.c.o
[2568/2839] Compiling C object app/test/dpdk-test.p/test_mbuf.c.o
[2569/2839] Compiling C object app/test/dpdk-test.p/test_cryptodev.c.o
[2570/2839] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_deq_tmo.c.o
[2571/2839] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_tx_enq.c.o
[2572/2839] Compiling C object drivers/libtmp_rte_event_octeontx2.a.p/event_octeontx2_otx2_worker.c.o
[2573/2839] Compiling C object drivers/libtmp_rte_event_octeontx2.a.p/event_octeontx2_otx2_worker_dual.c.o
[2574/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/18104/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-08-03 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 14:36 dpdklab [this message]
2021-08-04  1:25 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=20210803143634.41A3D89035@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --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).