From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Joyce Kong <joyce.kong@arm.com>
Subject: |FAILURE| pw133926 [PATCH] [v2] config/arm: correct cpu arch for cro
Date: Mon, 06 Nov 2023 20:01:42 -0800 (PST) [thread overview]
Message-ID: <6549b6a6.810a0220.6f93c.8297SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/133926
_Testing issues_
Submitter: Joyce Kong <joyce.kong@arm.com>
Date: Tuesday, November 07 2023 03:26:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2bbad8f974e00552d106c27e1d157a31179ab5ec
133926 --> testing fail
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | FAIL |
+----------------------------------------+--------------------+
==== 20 line log output for Ubuntu 20.04 aarch32 GCC Cross Compile (dpdk_meson_compile): ====
C compiler for the host machine: ccache arm-linux-gnueabihf-gcc (gcc 9.4.0 "arm-linux-gnueabihf-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0")
C linker for the host machine: arm-linux-gnueabihf-gcc ld.bfd 2.34
Build machine cpu family: x86_64
Build machine cpu: x86_64
Host machine cpu family: aarch32
Host machine cpu: auto
Target machine cpu family: aarch32
Target machine cpu: auto
Message: ## Building in Developer Mode ##
Program pkg-config found: YES (/usr/bin/pkg-config)
Program check-symbols.sh found: YES (/home-local/jenkins-local/jenkins-agent/workspace/Generic-DPDK-Compile-Meson@2/dpdk/buildtools/check-symbols.sh)
Program options-ibverbs-static.sh found: YES (/home-local/jenkins-local/jenkins-agent/workspace/Generic-DPDK-Compile-Meson@2/dpdk/buildtools/options-ibverbs-static.sh)
Program python3 found: YES (/usr/bin/python3)
Program cat found: YES (/usr/bin/cat)
Program ../buildtools/symlink-drivers-solibs.sh found: YES (/bin/sh /home-local/jenkins-local/jenkins-agent/workspace/Generic-DPDK-Compile-Meson@2/dpdk/config/../buildtools/symlink-drivers-solibs.sh)
Compiler for C supports arguments -march=native: NO
config/meson.build:178:8: ERROR: Problem encountered: Compiler does not support "native" arch flag.
A full log can be found at /home-local/jenkins-local/jenkins-agent/workspace/Generic-DPDK-Compile-Meson@2/dpdk/build/meson-logs/meson-log.txt
==== End log output ====
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 ARM GCC Cross Compile
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 Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28260/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-07 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 4:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-07 7:07 dpdklab
2023-11-07 5:30 dpdklab
2023-11-07 4:23 dpdklab
2023-11-07 4:11 dpdklab
2023-11-07 4:04 dpdklab
2023-11-07 4:04 dpdklab
2023-11-07 4:02 dpdklab
2023-11-07 4:02 dpdklab
2023-11-07 4:00 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=6549b6a6.810a0220.6f93c.8297SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=joyce.kong@arm.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).