From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw148465-148467 [PATCH] [v3,3/3] test/graph: fix graph aut
Date: Sat, 16 Nov 2024 08:55:13 -0800 (PST) [thread overview]
Message-ID: <6738ce71.050a0220.e85fd.5e20SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241114070432.3152188-3-kirankumark@marvell.com>
Test-Label: iol-unit-amd64-testing
Test-Status: WARNING
http://dpdk.org/patch/148467
_Testing issues_
Submitter: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Date: Thursday, November 14 2024 07:04:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:78383e9816a8efe2ba16ec2ce65d51b94e6114e7
148465-148467 --> testing issues
Upstream job id: Generic-VM-Unit-Test-DPDK#26251
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Fedora 39 (Clang) | PASS |
+---------------------+----------------+
| Debian 12 | WARN |
+---------------------+----------------+
| CentOS Stream 9 | WARN |
+---------------------+----------------+
| Fedora 39 | WARN |
+---------------------+----------------+
| Fedora 40 (Clang) | PASS |
+---------------------+----------------+
| Fedora 40 | WARN |
+---------------------+----------------+
| RHEL9 | WARN |
+---------------------+----------------+
| RHEL8 | WARN |
+---------------------+----------------+
| Ubuntu 24.04 | WARN |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
==== 20 line log output for Ubuntu 24.04 (dpdk_unit_test): ====
from ../lib/eal/include/rte_malloc.h:16,
from ../lib/graph/graph_populate.c:8:
In function 'memcpy',
inlined from 'graph_nodes_populate' at ../lib/graph/graph_populate.c:105:4,
inlined from 'graph_fp_mem_populate' at ../lib/graph/graph_populate.c:217:2,
inlined from 'graph_fp_mem_create' at ../lib/graph/graph_populate.c:239:9:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: error: 'parent' may be used uninitialized [-Werror=maybe-uninitialized]
29 | return __builtin___memcpy_chk (__dest, __src, __len,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 | __glibc_objsize0 (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/graph/graph_populate.c: In function 'graph_fp_mem_create':
../lib/graph/graph_populate.c:81:21: note: 'parent' was declared here
81 | const char *parent;
| ^~~~~~
cc1: all warnings being treated as errors
[508/3076] Compiling C object lib/librte_graph.a.p/graph_graph_stats.c.o
[509/3076] Compiling C object lib/librte_graph.a.p/graph_graph_pcap.c.o
[510/3076] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
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)
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 39
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
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)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
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
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.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/patchsets/31926/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-11-16 16:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241114070432.3152188-3-kirankumark@marvell.com>
2024-11-14 6:39 ` |SUCCESS| pw148465-148467 [PATCH v3 3/3] test/graph: fix graph autotest second run test failure qemudev
2024-11-14 6:43 ` qemudev
2024-11-14 7:06 ` |SUCCESS| pw148467 " checkpatch
2024-11-14 8:05 ` |FAILURE| " 0-day Robot
2024-11-14 9:35 ` |SUCCESS| pw148465-148467 [PATCH] [v3,3/3] test/graph: fix graph aut dpdklab
2024-11-14 9:54 ` dpdklab
2024-11-14 10:31 ` dpdklab
2024-11-14 10:33 ` dpdklab
2024-11-14 11:03 ` dpdklab
2024-11-14 15:47 ` |FAILURE| " dpdklab
2024-11-14 15:54 ` |PENDING| " dpdklab
2024-11-14 16:06 ` |WARNING| " dpdklab
2024-11-14 16:40 ` |SUCCESS| " dpdklab
2024-11-14 17:49 ` |FAILURE| " dpdklab
2024-11-14 17:49 ` dpdklab
2024-11-14 19:45 ` |SUCCESS| " dpdklab
2024-11-14 20:16 ` dpdklab
2024-11-14 20:35 ` dpdklab
2024-11-14 20:46 ` |WARNING| " dpdklab
2024-11-16 16:55 ` dpdklab [this message]
2024-11-16 17:11 ` 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=6738ce71.050a0220.e85fd.5e20SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).