From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |WARNING| [GIT MASTER] 7ce7d3341d7e21c2a81f2fea8e451681d7306d77
Date: Thu, 26 Dec 2024 00:16:47 -0800 (PST) [thread overview]
Message-ID: <676d10ef.630a0220.2670d7.8ac6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: tags/v22.11
7ce7d3341d7e21c2a81f2fea8e451681d7306d77 --> testing issues
Upstream job id: Generic-DPDK-Compile-Meson#346783
Test environment and result as below:
+---------------------+--------------------+-----------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_win_llvm_compile | dpdk_mingw64_compile |
+=====================+====================+=======================+======================+
| Debian Bullseye | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Debian 12 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Fedora 40 (Clang) | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Fedora 40 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Fedora 41 (Clang) | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Fedora 41 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| RHEL8 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| RHEL9 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Ubuntu 24.04 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| FreeBSD 13.4 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| FreeBSD 14.2 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Windows Server 2022 | SKIPPED | FAIL | PASS |
+---------------------+--------------------+-----------------------+----------------------+
==== 20 line log output for Windows Server 2022 (dpdk_win_llvm_compile): ====
..\lib\eal\include/rte_common.h:850:32: note: expanded from macro 'RTE_FMT_TAIL'
#define RTE_FMT_TAIL(fmt, ...) __VA_ARGS__
^~~~~~~~~~~
..\lib\eal\include/rte_common.h:848:39: note: expanded from macro 'RTE_FMT'
#define RTE_FMT(fmt, ...) fmt "%.0s", __VA_ARGS__ ""
^~~~~~~~~~~
../drivers/crypto/mlx5/mlx5_crypto.c:463:18: note: forward declaration of 'struct mlx5_err_cqe'
volatile struct mlx5_err_cqe *cqe = (volatile struct mlx5_err_cqe *)
^
3 errors generated.
[629/788] Compiling C object drivers/libtmp_rte_crypto_mlx5.a.p/crypto_mlx5_mlx5_crypto_dek.c.obj
[630/788] Generating rte_net_octeon_ep.pmd.c with a custom command (wrapped by meson to set PATH)
[631/788] Generating rte_net_vmxnet3.pmd.c with a custom command (wrapped by meson to set PATH)
[632/788] Compiling C object app/dpdk-testpmd.exe.p/test-pmd_cmdline_flow.c.obj
[633/788] Compiling C object app/test/dpdk-test.exe.p/test_cryptodev.c.obj
[634/788] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_empw.c.obj
[635/788] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_nompw.c.obj
[636/788] Compiling C object app/dpdk-testpmd.exe.p/test-pmd_config.c.obj
[637/788] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_txpp.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 41 (Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Fedora 41
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
openSUSE Leap 15
Kernel: Depends on container host
Compiler: gcc (SUSE Linux) 7.5.0
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
FreeBSD 13.4
Kernel: 13.4-RELEASE-p1
Compiler: clang 18.1.6
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/32052/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-26 8:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 8:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-27 8:33 dpdklab
2024-12-27 8:12 dpdklab
2024-12-26 8:07 dpdklab
2024-12-26 8:02 dpdklab
2024-12-25 9:26 dpdklab
2024-12-25 9:18 dpdklab
2024-12-25 8:58 dpdklab
2024-12-25 8:47 dpdklab
2024-12-25 8:38 dpdklab
2024-12-24 9:39 dpdklab
2024-12-24 9:04 dpdklab
2024-12-24 9:00 dpdklab
2024-12-24 9:00 dpdklab
2024-12-24 8:58 dpdklab
2024-12-24 8:55 dpdklab
2024-12-24 8:54 dpdklab
2024-12-24 8:53 dpdklab
2024-12-24 8:51 dpdklab
2024-12-24 8:48 dpdklab
2024-12-24 8:45 dpdklab
2024-12-23 8:32 dpdklab
2024-12-23 7:51 dpdklab
2024-12-23 7:35 dpdklab
2024-12-23 7:32 dpdklab
2024-12-22 7:50 dpdklab
2024-12-21 8:46 dpdklab
2024-12-21 8:21 dpdklab
2024-12-21 8:19 dpdklab
2024-12-21 7:58 dpdklab
2024-12-21 7:57 dpdklab
2024-12-20 10:07 dpdklab
2024-12-20 9:05 dpdklab
2024-12-19 8:05 dpdklab
2024-12-19 7:05 dpdklab
2024-12-18 16:42 dpdklab
2024-12-18 16:04 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=676d10ef.630a0220.2670d7.8ac6SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).