From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |FAILURE| pw125727-125728 [PATCH] [2/2] telemetry: use portable syntax to initialize array
Date: Mon, 3 Apr 2023 17:22:27 +0000 (UTC) [thread overview]
Message-ID: <20230403172227.1B2BB60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-x86_64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/125728
_Testing issues_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Monday, April 03 2023 16:30:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c682c8991963be243dcc3b7cdc9d6984a1961f4e
125727-125728 --> testing fail
Test environment and result as below:
+------------------+--------------------+
| Environment | dpdk_meson_compile |
+==================+====================+
| CentOS Stream 9 | FAIL |
+------------------+--------------------+
| Ubuntu 22.04 | FAIL |
+------------------+--------------------+
| Ubuntu 20.04 | FAIL |
+------------------+--------------------+
| RHEL 7 | FAIL |
+------------------+--------------------+
| openSUSE Leap 15 | FAIL |
+------------------+--------------------+
| RHEL8 | FAIL |
+------------------+--------------------+
| Debian Buster | FAIL |
+------------------+--------------------+
| Debian Bullseye | FAIL |
+------------------+--------------------+
| FreeBSD 13 | FAIL |
+------------------+--------------------+
| CentOS Stream 8 | FAIL |
+------------------+--------------------+
==== 20 line log output for CentOS Stream 8 (dpdk_meson_compile): ====
Build targets in project: 750
Option default_library is: shared [default: static]
Found ninja-1.11.1.git.kitware.jobserver-1 at /usr/local/bin/ninja
ninja: Entering directory `build'
[1/3242] Compiling C object 'lib/76b5a35@@rte_kvargs@sta/kvargs_rte_kvargs.c.o'.
[2/3242] Linking static target lib/librte_kvargs.a.
[3/3242] Generating kvargs.sym_chk with a meson_exe.py custom command.
[4/3242] Linking target lib/librte_kvargs.so.23.1.
[5/3242] Generating symbol file 'lib/76b5a35@@rte_kvargs@sha/librte_kvargs.so.23.1.symbols'.
[6/3242] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry.c.o'.
FAILED: lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry.c.o
ccache cc -Ilib/76b5a35@@rte_telemetry@sta -Ilib -I../lib -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_USE_FUNCTION_VERSIONING -DRTE_LOG_DEFAULT_LOGTYPE=lib.telemetry -MD -MQ 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry.c.o' -MF 'lib/76b5a35@@rte_telemetry@sta/t
elemetry_telemetry.c.o.d' -o 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry.c.o' -c ../lib/telemetry/telemetry.c
In file included from ../lib/telemetry/telemetry.c:24:
../lib/telemetry/telemetry_json.h: In function '__json_snprintf':
../lib/telemetry/telemetry_json.h:41:29: error: argument to 'sizeof' in 'vsnprintf' call is the same expression as the destination; did you mean to provide an explicit length? [-Werror=sizeof-pointer-memaccess]
ret = vsnprintf(tmp, sizeof(tmp), format, ap);
^
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25908/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-03 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 17:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-03 17:22 dpdklab
2023-04-03 17:11 dpdklab
2023-04-03 17:05 dpdklab
[not found] <1680539424-20255-3-git-send-email-roretzla@linux.microsoft.com>
2023-04-03 16:26 ` |FAILURE| pw125727-125728 [PATCH 2/2] " qemudev
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=20230403172227.1B2BB60095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=roretzla@linux.microsoft.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).