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] a6ec5765cf83d3d58cbd6d4ed5b92b4a06f8a808
Date: Fri, 02 Aug 2024 05:56:43 -0700 (PDT)	[thread overview]
Message-ID: <66acd78b.170a0220.347f9a.4f29SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v23.11

a6ec5765cf83d3d58cbd6d4ed5b92b4a06f8a808 --> testing issues

Upstream job id: Generic-Unit-Test-DPDK#248215

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 40           | PASS           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PEND           |
+---------------------+----------------+
| Ubuntu 22.04        | PEND           |
+---------------------+----------------+
| Ubuntu 24.04        | WARN           |
+---------------------+----------------+

==== 20 line log output for Ubuntu 24.04 (dpdk_unit_test): ====
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: error: argument 2 null where non-null expected [-Werror=nonnull]
29 |   return __builtin___memcpy_chk (__dest, __src, __len,
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 |                                  __glibc_objsize0 (__dest));
|                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: note: in a call to built-in function '__builtin___memcpy_chk'
In function 'memcpy',
inlined from 'pcapng_add_option' at ../lib/pcapng/rte_pcapng.c:131:2,
inlined from 'rte_pcapng_write_stats' at ../lib/pcapng/rte_pcapng.c:371:9:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: error: argument 2 null where non-null expected [-Werror=nonnull]
29 |   return __builtin___memcpy_chk (__dest, __src, __len,
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 |                                  __glibc_objsize0 (__dest));
|                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: note: in a call to built-in function '__builtin___memcpy_chk'
cc1: all warnings being treated as errors
[332/2791] Compiling C object 'lib/76b5a35@@rte_power@sta/power_power_acpi_cpufreq.c.o'.
[333/2791] Compiling C object 'lib/76b5a35@@rte_power@sta/power_power_amd_pstate_cpufreq.c.o'.
[334/2791] Generating member.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30113/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-08-02 12:56 UTC|newest]

Thread overview: 335+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 12:56 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-22  9:47 dpdklab
2024-08-22  9:45 dpdklab
2024-08-22  9:45 dpdklab
2024-08-22  9:45 dpdklab
2024-08-22  9:44 dpdklab
2024-08-22  9:43 dpdklab
2024-08-22  9:42 dpdklab
2024-08-22  9:42 dpdklab
2024-08-22  9:39 dpdklab
2024-08-22  9:37 dpdklab
2024-08-22  9:36 dpdklab
2024-08-22  9:35 dpdklab
2024-08-22  9:21 dpdklab
2024-08-22  9:20 dpdklab
2024-08-21  8:49 dpdklab
2024-08-21  8:38 dpdklab
2024-08-21  8:20 dpdklab
2024-08-21  8:19 dpdklab
2024-08-21  8:18 dpdklab
2024-08-21  8:15 dpdklab
2024-08-21  8:14 dpdklab
2024-08-21  8:12 dpdklab
2024-08-21  8:11 dpdklab
2024-08-21  8:07 dpdklab
2024-08-21  8:05 dpdklab
2024-08-21  8:04 dpdklab
2024-08-20 17:27 dpdklab
2024-08-20  8:46 dpdklab
2024-08-18  9:11 dpdklab
2024-08-18  8:37 dpdklab
2024-08-18  8:29 dpdklab
2024-08-18  7:23 dpdklab
2024-08-18  7:21 dpdklab
2024-08-18  7:20 dpdklab
2024-08-18  7:20 dpdklab
2024-08-18  7:20 dpdklab
2024-08-17 10:34 dpdklab
2024-08-17  8:24 dpdklab
2024-08-17  7:22 dpdklab
2024-08-17  7:21 dpdklab
2024-08-17  7:21 dpdklab
2024-08-17  7:20 dpdklab
2024-08-17  7:19 dpdklab
2024-08-17  7:16 dpdklab
2024-08-17  6:54 dpdklab
2024-08-17  6:53 dpdklab
2024-08-17  6:52 dpdklab
2024-08-17  6:52 dpdklab
2024-08-17  6:51 dpdklab
2024-08-17  6:50 dpdklab
2024-08-17  6:49 dpdklab
2024-08-16  9:31 dpdklab
2024-08-16  9:31 dpdklab
2024-08-16  8:02 dpdklab
2024-08-16  8:02 dpdklab
2024-08-16  8:01 dpdklab
2024-08-16  8:01 dpdklab
2024-08-16  8:00 dpdklab
2024-08-16  8:00 dpdklab
2024-08-16  8:00 dpdklab
2024-08-16  7:59 dpdklab
2024-08-16  7:59 dpdklab
2024-08-16  7:59 dpdklab
2024-08-16  7:59 dpdklab
2024-08-16  7:57 dpdklab
2024-08-16  7:56 dpdklab
2024-08-15 10:05 dpdklab
2024-08-15 10:00 dpdklab
2024-08-15  9:58 dpdklab
2024-08-15  9:58 dpdklab
2024-08-15  9:55 dpdklab
2024-08-15  9:52 dpdklab
2024-08-15  9:48 dpdklab
2024-08-15  9:45 dpdklab
2024-08-15  9:42 dpdklab
2024-08-15  9:40 dpdklab
2024-08-15  9:40 dpdklab
2024-08-15  9:38 dpdklab
2024-08-15  9:38 dpdklab
2024-08-15  9:37 dpdklab
2024-08-15  6:53 dpdklab
2024-08-15  6:46 dpdklab
2024-08-15  6:46 dpdklab
2024-08-15  6:46 dpdklab
2024-08-15  6:45 dpdklab
2024-08-15  6:42 dpdklab
2024-08-15  6:42 dpdklab
2024-08-14  8:59 dpdklab
2024-08-14  8:44 dpdklab
2024-08-14  8:41 dpdklab
2024-08-14  8:40 dpdklab
2024-08-14  8:40 dpdklab
2024-08-14  6:42 dpdklab
2024-08-13 12:09 dpdklab
2024-08-13 12:04 dpdklab
2024-08-13 11:58 dpdklab
2024-08-13 11:57 dpdklab
2024-08-13 11:57 dpdklab
2024-08-13 11:16 dpdklab
2024-08-13 10:03 dpdklab
2024-08-13 10:00 dpdklab
2024-08-13 10:00 dpdklab
2024-08-13  9:57 dpdklab
2024-08-13  9:54 dpdklab
2024-08-12  7:14 dpdklab
2024-08-12  6:52 dpdklab
2024-08-12  5:38 dpdklab
2024-08-12  5:38 dpdklab
2024-08-12  5:37 dpdklab
2024-08-12  5:36 dpdklab
2024-08-12  5:35 dpdklab
2024-08-11  8:03 dpdklab
2024-08-11  7:51 dpdklab
2024-08-11  7:51 dpdklab
2024-08-11  7:05 dpdklab
2024-08-11  6:34 dpdklab
2024-08-11  6:31 dpdklab
2024-08-10 17:19 dpdklab
2024-08-10  7:15 dpdklab
2024-08-10  7:09 dpdklab
2024-08-10  7:03 dpdklab
2024-08-10  7:03 dpdklab
2024-08-10  5:46 dpdklab
2024-08-10  5:22 dpdklab
2024-08-09 14:07 dpdklab
2024-08-09 13:25 dpdklab
2024-08-09 13:23 dpdklab
2024-08-09 12:42 dpdklab
2024-08-09 12:39 dpdklab
2024-08-09 12:38 dpdklab
2024-08-09 12:37 dpdklab
2024-08-08  5:39 dpdklab
2024-08-08  5:39 dpdklab
2024-08-08  5:23 dpdklab
2024-08-08  5:18 dpdklab
2024-08-07  5:44 dpdklab
2024-08-07  5:40 dpdklab
2024-08-07  5:33 dpdklab
2024-08-07  5:32 dpdklab
2024-08-07  5:30 dpdklab
2024-08-07  5:25 dpdklab
2024-08-07  5:24 dpdklab
2024-08-06  6:41 dpdklab
2024-08-06  6:37 dpdklab
2024-08-06  6:35 dpdklab
2024-08-06  6:35 dpdklab
2024-08-06  6:21 dpdklab
2024-08-06  5:45 dpdklab
2024-08-06  5:43 dpdklab
2024-08-06  5:40 dpdklab
2024-08-06  5:38 dpdklab
2024-08-05  5:57 dpdklab
2024-08-05  5:48 dpdklab
2024-08-05  5:48 dpdklab
2024-08-05  5:40 dpdklab
2024-08-05  5:39 dpdklab
2024-08-05  5:38 dpdklab
2024-08-04  5:23 dpdklab
2024-08-04  5:20 dpdklab
2024-08-04  5:20 dpdklab
2024-08-04  5:15 dpdklab
2024-08-03  5:44 dpdklab
2024-08-03  5:38 dpdklab
2024-08-03  5:37 dpdklab
2024-08-03  5:36 dpdklab
2024-08-03  5:22 dpdklab
2024-08-03  5:18 dpdklab
2024-08-03  5:17 dpdklab
2024-08-02 13:09 dpdklab
2024-08-02 13:06 dpdklab
2024-08-02 12:57 dpdklab
2024-08-02 12:15 dpdklab
2024-08-02 12:10 dpdklab
2024-08-02 12:03 dpdklab
2024-08-02 12:00 dpdklab
2024-08-02 11:55 dpdklab
2024-08-01  8:37 dpdklab
2024-08-01  8:35 dpdklab
2024-08-01  8:34 dpdklab
2024-08-01  8:34 dpdklab
2024-08-01  8:23 dpdklab
2024-08-01  7:18 dpdklab
2024-07-31  5:53 dpdklab
2024-07-31  5:43 dpdklab
2024-07-31  5:38 dpdklab
2024-07-31  5:36 dpdklab
2024-07-31  5:09 dpdklab
2024-07-31  5:07 dpdklab
2024-07-31  5:03 dpdklab
2024-07-31  5:02 dpdklab
2024-07-30  6:48 dpdklab
2024-07-30  5:50 dpdklab
2024-07-30  5:48 dpdklab
2024-07-30  5:42 dpdklab
2024-07-30  5:19 dpdklab
2024-07-30  5:16 dpdklab
2024-07-30  5:15 dpdklab
2024-07-29  5:25 dpdklab
2024-07-29  5:25 dpdklab
2024-07-29  5:23 dpdklab
2024-07-29  5:21 dpdklab
2024-07-29  5:21 dpdklab
2024-07-28  6:31 dpdklab
2024-07-28  6:20 dpdklab
2024-07-28  6:18 dpdklab
2024-07-28  6:17 dpdklab
2024-07-28  5:58 dpdklab
2024-07-28  5:45 dpdklab
2024-07-28  5:41 dpdklab
2024-07-27  5:41 dpdklab
2024-07-27  5:38 dpdklab
2024-07-27  5:31 dpdklab
2024-07-27  5:30 dpdklab
2024-07-27  5:29 dpdklab
2024-07-27  5:01 dpdklab
2024-07-26  9:37 dpdklab
2024-07-26  9:34 dpdklab
2024-07-26  9:29 dpdklab
2024-07-26  9:26 dpdklab
2024-07-26  9:23 dpdklab
2024-07-26  8:41 dpdklab
2024-07-26  8:32 dpdklab
2024-07-26  8:28 dpdklab
2024-07-26  8:28 dpdklab
2024-07-26  8:25 dpdklab
2024-07-26  8:24 dpdklab
2024-07-25 15:20 dpdklab
2024-07-25 15:10 dpdklab
2024-07-25 15:03 dpdklab
2024-07-25 14:59 dpdklab
2024-07-25 13:37 dpdklab
2024-07-24  7:34 dpdklab
2024-07-24  5:45 dpdklab
2024-07-23  7:56 dpdklab
2024-07-23  7:51 dpdklab
2024-07-23  7:51 dpdklab
2024-07-23  7:50 dpdklab
2024-07-23  7:35 dpdklab
2024-07-23  6:43 dpdklab
2024-07-23  6:41 dpdklab
2024-07-23  6:40 dpdklab
2024-07-23  6:39 dpdklab
2024-07-23  6:38 dpdklab
2024-07-22  5:08 dpdklab
2024-07-22  5:05 dpdklab
2024-07-22  5:02 dpdklab
2024-07-22  4:58 dpdklab
2024-07-22  4:57 dpdklab
2024-07-22  4:57 dpdklab
2024-07-21  5:37 dpdklab
2024-07-21  5:31 dpdklab
2024-07-21  5:31 dpdklab
2024-07-21  5:28 dpdklab
2024-07-21  5:27 dpdklab
2024-07-21  5:21 dpdklab
2024-07-21  5:20 dpdklab
2024-07-21  5:19 dpdklab
2024-07-21  5:18 dpdklab
2024-07-20  6:45 dpdklab
2024-07-20  6:38 dpdklab
2024-07-20  6:37 dpdklab
2024-07-20  6:36 dpdklab
2024-07-20  6:26 dpdklab
2024-07-20  5:48 dpdklab
2024-07-20  5:42 dpdklab
2024-07-20  5:42 dpdklab
2024-07-20  5:41 dpdklab
2024-07-19  5:58 dpdklab
2024-07-19  5:55 dpdklab
2024-07-19  5:50 dpdklab
2024-07-19  5:48 dpdklab
2024-07-19  5:16 dpdklab
2024-07-19  5:15 dpdklab
2024-07-19  5:14 dpdklab
2024-07-18 10:22 dpdklab
2024-07-18  9:14 dpdklab
2024-07-18  6:44 dpdklab
2024-07-18  6:23 dpdklab
2024-07-18  6:22 dpdklab
2024-07-18  6:22 dpdklab
2024-07-18  6:20 dpdklab
2024-07-17  9:32 dpdklab
2024-07-17  9:32 dpdklab
2024-07-17  9:31 dpdklab
2024-07-17  9:30 dpdklab
2024-07-17  9:29 dpdklab
2024-07-16  8:51 dpdklab
2024-07-16  8:19 dpdklab
2024-07-16  7:23 dpdklab
2024-07-16  7:17 dpdklab
2024-07-15  5:53 dpdklab
2024-07-15  5:11 dpdklab
2024-07-15  5:08 dpdklab
2024-07-14  6:09 dpdklab
2024-07-14  6:05 dpdklab
2024-07-14  5:58 dpdklab
2024-07-14  5:57 dpdklab
2024-07-14  5:52 dpdklab
2024-07-14  5:52 dpdklab
2024-07-14  5:51 dpdklab
2024-07-13  9:26 dpdklab
2024-07-13  9:17 dpdklab
2024-07-13  6:50 dpdklab
2024-07-13  6:40 dpdklab
2024-07-13  6:38 dpdklab
2024-07-13  6:36 dpdklab
2024-07-12  8:15 dpdklab
2024-07-12  8:09 dpdklab
2024-07-12  8:07 dpdklab
2024-07-12  8:05 dpdklab
2024-07-12  7:12 dpdklab
2024-07-12  6:15 dpdklab
2024-07-12  6:14 dpdklab
2024-07-12  5:58 dpdklab
2024-07-11 16:28 dpdklab
2024-07-11 15:37 dpdklab
2024-07-11  5:59 dpdklab
2024-07-11  5:58 dpdklab
2024-07-11  5:57 dpdklab
2024-07-11  5:55 dpdklab
2024-07-11  5:53 dpdklab
2024-07-11  5:52 dpdklab
2024-07-11  5:51 dpdklab
2024-07-11  5:46 dpdklab
2024-07-10 10:17 dpdklab
2024-07-10 10:13 dpdklab
2024-07-10 10:12 dpdklab
2024-07-10 10:12 dpdklab
2024-07-10 10:10 dpdklab
2024-07-10  9:10 dpdklab
2024-07-10  9:04 dpdklab
2024-07-10  8:58 dpdklab
2024-07-10  8:49 dpdklab
2024-07-10  8:47 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=66acd78b.170a0220.347f9a.4f29SMTPIN_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).