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: |FAILURE| [GIT MASTER] b40fd60a9d5b99d165aeeb09a43df2e404d9ec05
Date: Wed, 28 Aug 2024 12:47:46 -0700 (PDT) [thread overview]
Message-ID: <66cf7ee2.050a0220.2aa07c.040eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: 21.11-staging
b40fd60a9d5b99d165aeeb09a43df2e404d9ec05 --> testing issues
Upstream job id: Generic-DPDK-Compile-Meson#293253
Test environment and result as below:
+---------------------+--------------------+-----------------------+
| Environment | dpdk_meson_compile | dpdk_win_llvm_compile |
+=====================+====================+=======================+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+-----------------------+
| Debian 12 | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| Fedora 38 (Clang) | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+-----------------------+
| Fedora 38 | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| Fedora 39 (Clang) | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| Fedora 40 (Clang) | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| Fedora 39 | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| RHEL8 | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| Fedora 40 | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| RHEL9 | PASS | SKIPPED |
+---------------------+--------------------+-----------------------+
| Ubuntu 22.04 | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| Ubuntu 24.04 | FAIL | SKIPPED |
+---------------------+--------------------+-----------------------+
| Ubuntu 20.04 | PEND | SKIPPED |
+---------------------+--------------------+-----------------------+
| Windows Server 2022 | SKIPPED | PEND |
+---------------------+--------------------+-----------------------+
==== 20 line log output for Ubuntu 24.04 (dpdk_meson_compile): ====
inlined from 'pcapng_add_option' at ../lib/pcapng/rte_pcapng.c:112:2,
inlined from 'pcapng_section_block' at ../lib/pcapng/rte_pcapng.c:175:8,
inlined from 'rte_pcapng_fdopen' at ../lib/pcapng/rte_pcapng.c:626:6:
/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:112:2,
inlined from 'rte_pcapng_write_stats' at ../lib/pcapng/rte_pcapng.c:350: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
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
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
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)
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)
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
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
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/30383/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-08-28 19:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 19:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-19 16:56 dpdklab
2024-08-28 21:14 dpdklab
2024-08-28 20:53 dpdklab
2024-08-28 20:34 dpdklab
2024-08-28 20:29 dpdklab
2024-08-28 20:26 dpdklab
2024-08-28 20:26 dpdklab
2024-08-28 20:19 dpdklab
2024-08-28 20:15 dpdklab
2024-08-28 20:14 dpdklab
2024-08-28 20:04 dpdklab
2024-08-28 20:04 dpdklab
2024-08-28 20:01 dpdklab
2024-08-28 19:53 dpdklab
2024-08-28 19:48 dpdklab
2024-08-28 19:47 dpdklab
2024-08-28 19:46 dpdklab
2024-08-28 19:38 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=66cf7ee2.050a0220.2aa07c.040eSMTPIN_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).