From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Bruce Richardson <bruce.richardson@intel.com>
Subject: |FAILURE| pw131096-131097 [PATCH] [2/2] build: fail if explicitly re
Date: Fri, 01 Sep 2023 14:26:52 -0700 (PDT) [thread overview]
Message-ID: <64f2571c.250a0220.7c28b.beb4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/131097
_Testing issues_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, September 01 2023 14:23:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:62774b78a84e9fa5df56d04cffed69bef8c901f1
131096-131097 --> testing fail
Test environment and result as below:
+-----------------------------+----------------+
| Environment | dpdk_unit_test |
+=============================+================+
| 32-bit Ubuntu 20.04.4 (ARM) | FAIL |
+-----------------------------+----------------+
==== 20 line log output for 32-bit Ubuntu 20.04.4 (ARM) (dpdk_unit_test): ====
Compiler for C supports arguments -Wmissing-prototypes: YES
Compiler for C supports arguments -Wnested-externs: YES
Compiler for C supports arguments -Wold-style-definition: YES
Compiler for C supports arguments -Wpointer-arith: YES
Compiler for C supports arguments -Wsign-compare: YES
Compiler for C supports arguments -Wstrict-prototypes: YES
Compiler for C supports arguments -Wundef: YES
Compiler for C supports arguments -Wwrite-strings: YES
Compiler for C supports arguments -Wno-address-of-packed-member: YES
Compiler for C supports arguments -Wno-packed-not-aligned: YES
Compiler for C supports arguments -Wno-missing-field-initializers: YES
Compiler for C supports arguments -Wno-zero-length-bounds: YES
Compiler for C supports arguments -Wno-pointer-to-int-cast: YES
Message: Arm implementer: Generic armv8
Message: Arm part number: generic_aarch32
Compiler for C supports arguments -march=armv8-a: NO
config/arm/meson.build:714:12: ERROR: Problem encountered: No suitable armv8 march version found.
A full log can be found at /home-local/jenkins-local/workspace/Aarch32-Unit-Test/dpdk/build/meson-logs/meson-log.txt
==== End log output ====
32-bit Ubuntu 20.04.4 (ARM)
Kernel: 5.4.0-155-generic aarch64
Compiler: gcc 9.4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27507/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-01 21:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 21:26 dpdklab [this message]
2023-09-01 21:57 dpdklab
2023-09-14 10:10 dpdklab
2023-09-14 10:10 dpdklab
2023-09-14 10:13 dpdklab
2023-09-14 10:14 dpdklab
2023-09-14 10:26 dpdklab
2023-09-14 10:26 dpdklab
2023-09-14 10:27 dpdklab
2023-09-14 10:31 dpdklab
2023-09-14 10:47 dpdklab
2023-09-14 10:47 dpdklab
2023-09-19 16:31 dpdklab
2023-09-19 16:32 dpdklab
2023-09-19 16:32 dpdklab
2023-09-19 16:33 dpdklab
2023-09-19 16:40 dpdklab
2023-09-19 16:42 dpdklab
2023-09-19 16:43 dpdklab
2023-09-19 18:26 dpdklab
2023-09-19 18:27 dpdklab
2023-09-19 18:27 dpdklab
2023-09-19 18:27 dpdklab
2023-09-19 18:29 dpdklab
2023-09-19 18:30 dpdklab
2023-09-19 18:47 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=64f2571c.250a0220.7c28b.beb4SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=dpdk-test-reports@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).