automatic DPDK test reports
 help / color / mirror / Atom feed
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] 92bac8b798fa9c94bcf835bc49b4f16f1b0997fa
Date: Mon, 16 Dec 2024 23:51:48 -0800 (PST)	[thread overview]
Message-ID: <67612d94.170a0220.153987.561eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v22.11

92bac8b798fa9c94bcf835bc49b4f16f1b0997fa --> testing issues

Upstream job id: Generic-DPDK-Compile-Meson#343975

Test environment and result as below:

+---------------------+--------------------+-----------------------+
|     Environment     | dpdk_meson_compile | dpdk_win_llvm_compile |
+=====================+====================+=======================+
| Fedora 39 (Clang)   | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| Fedora 39           | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| RHEL8               | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| Ubuntu 22.04        | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| Ubuntu 24.04        | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| FreeBSD 13.4        | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| FreeBSD 14.2        | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| Debian 12           | PEND               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| CentOS Stream 9     | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| Fedora 40           | PASS               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| RHEL9               | PEND               | SKIPPED               |
+---------------------+--------------------+-----------------------+
| Windows Server 2022 | SKIPPED            | FAIL                  |
+---------------------+--------------------+-----------------------+

==== 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.
[617/788] Compiling C object drivers/libtmp_rte_net_vmxnet3.a.p/net_vmxnet3_vmxnet3_rxtx.c.obj
[618/788] Compiling C object drivers/libtmp_rte_net_vmxnet3.a.p/net_vmxnet3_vmxnet3_ethdev.c.obj
[619/788] Linking static target drivers/libtmp_rte_net_octeon_ep.a
[620/788] Compiling C object drivers/libtmp_rte_crypto_mlx5.a.p/crypto_mlx5_mlx5_crypto_dek.c.obj
[621/788] Compiling C object app/dpdk-testpmd.exe.p/test-pmd_csumonly.c.obj
[622/788] Compiling C object app/dpdk-testpmd.exe.p/test-pmd_cmdline_tm.c.obj
[623/788] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_nompw.c.obj
[624/788] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_empw.c.obj
[625/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 ====

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

openSUSE Leap 15
	Kernel: Depends on container host
	Compiler: gcc (SUSE Linux) 7.5.0

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

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.2.0-23ubuntu4) 13.2.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

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

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/31948/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-12-17  7:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  7:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-17  9:12 dpdklab
2024-12-17  8:23 dpdklab
2024-12-17  7:58 dpdklab
2024-12-17  7:50 dpdklab
2024-12-16 21:58 dpdklab
2024-12-15  8:23 dpdklab
2024-12-15  8:20 dpdklab
2024-12-15  0:26 dpdklab
2024-12-15  0:18 dpdklab
2024-12-14 17:59 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=67612d94.170a0220.153987.561eSMTPIN_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).