From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Morten Brorup <mb@smartsharesystems.com>
Subject: |FAILURE| pw144369 [PATCH] [RFC,v3] mempool: obey configured cache s
Date: Sat, 21 Sep 2024 09:04:20 -0700 (PDT) [thread overview]
Message-ID: <66eeee84.6b0a0220.210e01.48adSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240920171350.841532-1-mb@smartsharesystems.com>
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/144369
_Testing issues_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Friday, September 20 2024 17:13:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
144369 --> testing issues
Upstream job id: Generic-DPDK-Compile-Meson#304453
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| RHEL9 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | FAIL |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | FAIL |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Fedora 40 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Fedora 40 (ARM Clang) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM) | FAIL |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PEND |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | FAIL |
+----------------------------------------+--------------------+
| Debian 12 (arm) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | FAIL |
+----------------------------------------+--------------------+
| Fedora 39 (ARM Clang) | FAIL |
+----------------------------------------+--------------------+
==== 20 line log output for Fedora 39 (ARM Clang) (dpdk_meson_compile): ====
376 | #define __rte_noinline __attribute__((noinline))
| ^~~~~~~~
../drivers/common/dpaax/compat.h:58:18: note: expanded from macro 'noinline'
58 | #define noinline __rte_noinline
| ^~~~~~~~~~~~~~
In file included from ../drivers/bus/dpaa/base/qbman/bman_driver.c:10:
In file included from ../drivers/bus/dpaa/include/fsl_usd.h:14:
In file included from ../drivers/bus/dpaa/include/fsl_qman.h:17:
In file included from ../lib/eventdev/rte_eventdev.h:248:
../lib/mempool/rte_mempool.h:1536:8: error: unknown attribute '__rte_noinline' ignored [-Werror,-Wunknown-attributes]
1536 | static __rte_noinline int
| ^~~~~~~~~~~~~~
../lib/eal/include/rte_common.h:376:39: note: expanded from macro '__rte_noinline'
376 | #define __rte_noinline __attribute__((noinline))
| ^~~~~~~~
../drivers/common/dpaax/compat.h:58:18: note: expanded from macro 'noinline'
58 | #define noinline __rte_noinline
| ^~~~~~~~~~~~~~
2 errors generated.
ninja: build stopped: subcommand failed.
==== End log output ====
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: Depends on container host
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
Ubuntu 22.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
Fedora 40 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
Ubuntu 20.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 24.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
CentOS Stream 9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian 11 (Buster) (ARM)
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: Depends on container host
Compiler: clang 10.0.0-4ubuntu1
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: Depends on container host
Compiler: gcc 9.4.0
Fedora 39 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31104/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-09-21 16:04 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240920171350.841532-1-mb@smartsharesystems.com>
2024-09-20 16:47 ` |SUCCESS| pw144369 [RFC PATCH v3] mempool: obey configured cache size qemudev
2024-09-20 16:51 ` qemudev
2024-09-20 17:14 ` |WARNING| " checkpatch
2024-09-20 17:48 ` |FAILURE| " 0-day Robot
2024-09-21 15:40 ` |FAILURE| pw144369 [PATCH] [RFC,v3] mempool: obey configured cache s dpdklab
2024-09-21 15:41 ` dpdklab
2024-09-21 15:42 ` dpdklab
2024-09-21 15:42 ` dpdklab
2024-09-21 15:43 ` dpdklab
2024-09-21 15:44 ` dpdklab
2024-09-21 15:44 ` dpdklab
2024-09-21 15:45 ` dpdklab
2024-09-21 15:47 ` dpdklab
2024-09-21 15:47 ` dpdklab
2024-09-21 15:48 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:50 ` dpdklab
2024-09-21 15:50 ` |SUCCESS| " dpdklab
2024-09-21 15:50 ` |FAILURE| " dpdklab
2024-09-21 15:50 ` dpdklab
2024-09-21 15:50 ` dpdklab
2024-09-21 15:52 ` |WARNING| " dpdklab
2024-09-21 15:53 ` dpdklab
2024-09-21 15:53 ` |FAILURE| " dpdklab
2024-09-21 15:54 ` dpdklab
2024-09-21 15:54 ` dpdklab
2024-09-21 15:54 ` dpdklab
2024-09-21 15:54 ` dpdklab
2024-09-21 15:58 ` |SUCCESS| " dpdklab
2024-09-21 16:03 ` |FAILURE| " dpdklab
2024-09-21 16:03 ` dpdklab
2024-09-21 16:04 ` |WARNING| " dpdklab
2024-09-21 16:04 ` dpdklab
2024-09-21 16:04 ` |FAILURE| " dpdklab
2024-09-21 16:04 ` dpdklab [this message]
2024-09-21 16:04 ` dpdklab
2024-09-21 16:04 ` dpdklab
2024-09-21 16:04 ` |WARNING| " dpdklab
2024-09-21 16:04 ` |FAILURE| " dpdklab
2024-09-21 16:04 ` dpdklab
2024-09-21 16:05 ` dpdklab
2024-09-21 16:06 ` dpdklab
2024-09-21 16:19 ` |SUCCESS| " dpdklab
2024-09-21 16:22 ` dpdklab
2024-09-21 16:25 ` dpdklab
2024-09-21 16:54 ` dpdklab
2024-09-21 18:45 ` |WARNING| " dpdklab
2024-09-23 17:49 ` |SUCCESS| " dpdklab
2024-09-23 21:35 ` 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=66eeee84.6b0a0220.210e01.48adSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mb@smartsharesystems.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).