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| pw144891 [PATCH] [RFC,v15] mempool: fix mempool cache size
Date: Wed, 02 Oct 2024 04:58:35 -0700 (PDT) [thread overview]
Message-ID: <66fd356b.630a0220.1f9604.f139SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241002112506.2425092-1-mb@smartsharesystems.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/144891
_Testing issues_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Wednesday, October 02 2024 11:25:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b3846244b2b9245356d398d802ba3c975b2f4f63
144891 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#269060
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PEND |
+---------------------+----------------+
| CentOS Stream 9 | PEND |
+---------------------+----------------+
| Debian 12 | WARN |
+---------------------+----------------+
| Debian Bullseye | PEND |
+---------------------+----------------+
| Fedora 37 | PEND |
+---------------------+----------------+
| Fedora 39 | PEND |
+---------------------+----------------+
| Fedora 38 | PEND |
+---------------------+----------------+
| Fedora 38 (Clang) | PEND |
+---------------------+----------------+
==== 20 line log output for Debian 12 (dpdk_unit_test): ====
Compiler for C supports arguments -Wformat-nonliteral: YES
Compiler for C supports arguments -Wformat-security: YES
Compiler for C supports arguments -Wmissing-declarations: YES
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 -Waddress-of-packed-member: YES
Compiler for C supports arguments -Wno-packed-not-aligned -Wpacked-not-aligned: YES
Compiler for C supports arguments -Wno-missing-field-initializers -Wmissing-field-initializers: YES
Compiler for C supports arguments -Wno-zero-length-bounds -Wzero-length-bounds: YES
Program /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/config/arm/armv8_machine.py found: YES (/home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/config/arm/armv8_machine.py)
config/arm/meson.build:767:16: ERROR: Problem encountered: Error when getting Arm Implementer ID and part number.
A full log can be found at /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/meson-log.txt
==== End log output ====
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31219/
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-10-02 11:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241002112506.2425092-1-mb@smartsharesystems.com>
2024-10-02 10:58 ` |SUCCESS| pw144891 [RFC PATCH v15] " qemudev
2024-10-02 11:03 ` |FAILURE| " qemudev
2024-10-02 11:25 ` |SUCCESS| " checkpatch
2024-10-02 11:58 ` dpdklab [this message]
2024-10-02 12:03 ` |SUCCESS| pw144891 [PATCH] [RFC,v15] " dpdklab
2024-10-02 12:16 ` dpdklab
2024-10-02 12:17 ` |PENDING| " dpdklab
2024-10-02 12:18 ` |SUCCESS| " dpdklab
2024-10-02 12:21 ` dpdklab
2024-10-02 12:21 ` dpdklab
2024-10-02 12:24 ` |PENDING| " dpdklab
2024-10-02 12:26 ` |FAILURE| pw144891 [RFC PATCH v15] " 0-day Robot
2024-10-02 12:26 ` |SUCCESS| pw144891 [PATCH] [RFC,v15] " dpdklab
2024-10-02 12:28 ` dpdklab
2024-10-02 12:28 ` |FAILURE| " dpdklab
2024-10-02 12:29 ` dpdklab
2024-10-02 12:38 ` dpdklab
2024-10-02 12:46 ` dpdklab
2024-10-02 12:48 ` dpdklab
2024-10-02 12:51 ` dpdklab
2024-10-02 13:00 ` dpdklab
2024-10-02 13:05 ` |SUCCESS| " dpdklab
2024-10-02 13:09 ` |FAILURE| " dpdklab
2024-10-02 13:13 ` dpdklab
2024-10-02 13:24 ` |PENDING| " dpdklab
2024-10-02 13:25 ` |SUCCESS| " dpdklab
2024-10-02 13:45 ` dpdklab
2024-10-02 14:14 ` dpdklab
2024-10-02 16:08 ` |FAILURE| " dpdklab
2024-10-02 17:27 ` |SUCCESS| " dpdklab
2024-10-02 17:35 ` |FAILURE| " 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=66fd356b.630a0220.1f9604.f139SMTPIN_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).