From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Artemy Kovalyov <artemyko@nvidia.com>
Subject: |FAILURE| pw135049-135053 [PATCH] [5/5] eal: fix memzone fbarray cle
Date: Mon, 11 Dec 2023 21:14:11 -0800 (PST) [thread overview]
Message-ID: <6577ec23.050a0220.493b5.3cbdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/135053
_Testing issues_
Submitter: Artemy Kovalyov <artemyko@nvidia.com>
Date: Tuesday, December 12 2023 04:25:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
135049-135053 --> testing fail
Test environment and result as below:
+--------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE | FAIL |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM) | FAIL |
+--------------------------+--------------------+
| Fedora 38 (ARM) | FAIL |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM) | FAIL |
+--------------------------+--------------------+
| Fedora 37 (ARM) | FAIL |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | FAIL |
+--------------------------+--------------------+
==== 20 line log output for Debian 11 (Buster) (ARM) (dpdk_meson_compile): ====
| ^~~~~~~~~~~~~~
../app/test-mp/main.c:37:40: error: nested extern declaration of 'rte_get_tsc_hz' [-Werror=nested-externs]
In file included from ../lib/eal/include/rte_stdatomic.h:8,
from ../lib/eal/include/generic/rte_atomic.h:18,
from ../lib/eal/arm/include/rte_atomic_64.h:17,
from ../lib/eal/arm/include/rte_atomic.h:9,
from ../lib/eal/include/generic/rte_pause.h:19,
from ../lib/eal/arm/include/rte_pause_64.h:19,
from ../lib/eal/arm/include/rte_pause.h:13,
from ../lib/eal/include/generic/rte_rwlock.h:34,
from ../lib/eal/arm/include/rte_rwlock.h:12,
from ../lib/eal/include/rte_eal_memconfig.h:10,
from ../lib/eal/include/rte_memory.h:25,
from ../lib/eal/include/rte_malloc.h:16,
from ../app/test-mp/main.c:4:
../app/test-mp/main.c:40:23: error: comparison of integer expressions of different signedness: 'int' and 'uint64_t' {aka 'long unsigned int'} [-Werror=sign-compare]
40 | assert(rte_rdtsc() < timeout);
| ^
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== 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)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28593/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-12 5:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 5:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-12 7:56 dpdklab
2023-12-12 5:29 dpdklab
2023-12-12 5:29 dpdklab
2023-12-12 5:28 dpdklab
2023-12-12 5:27 dpdklab
2023-12-12 5:26 dpdklab
2023-12-12 5:22 dpdklab
2023-12-12 5:21 dpdklab
2023-12-12 5:20 dpdklab
2023-12-12 5:19 dpdklab
2023-12-12 5:19 dpdklab
2023-12-12 5:17 dpdklab
2023-12-12 5:16 dpdklab
2023-12-12 5:14 dpdklab
2023-12-12 5:12 dpdklab
2023-12-12 5:11 dpdklab
2023-12-12 5:11 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=6577ec23.050a0220.493b5.3cbdSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=artemyko@nvidia.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).