From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chenbo Xia <chenbox@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw159399 [PATCH] [RFC] net/virtio: avoid global variable n
Date: Sun, 11 Jan 2026 13:00:42 -0800 (PST) [thread overview]
Message-ID: <69640f7a.050a0220.2fe741.d0a4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251222004446.62076-1-stephen@networkplumber.org>
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/159399
_Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, December 22 2025 00:44:46
DPDK git baseline: Repo:dpdk-next-virtio
Branch: master
CommitID:6b37c26a95388aa41bb5267c7c42f604fd571a38
159399 --> testing issues
Upstream job id: Generic-DPDK-Compile-Meson#455248
Test environment and result as below:
+-----------------+--------------------+
| Environment | dpdk_meson_compile |
+=================+====================+
| Fedora Linux 43 | FAIL |
+-----------------+--------------------+
==== 20 line log output for Fedora Linux 43 (dpdk_meson_compile): ====
46 | (RTE_TRACE_POINT_ARGS_(RTE_TRACE_POINT_ARGS_COUNT(0, __VA_ARGS__), __VA_ARGS__))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_trace_point_register.h:44:30: note: expanded from macro 'RTE_TRACE_POINT_ARGS_'
44 | RTE_TRACE_POINT_ARGS_EXPAND(RTE_TRACE_POINT_ARGS_FUNC(N))(__VA_ARGS__)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_trace_point_register.h:41:38: note: expanded from macro 'RTE_TRACE_POINT_ARGS_FUNC'
41 | #define RTE_TRACE_POINT_ARGS_FUNC(a) RTE_TRACE_POINT_ARGS_ ## a
| ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../lib/eal/include/rte_trace_point_register.h:42:42: note: expanded from macro 'RTE_TRACE_POINT_ARGS_EXPAND'
42 | #define RTE_TRACE_POINT_ARGS_EXPAND(...) __VA_ARGS__
| ^
../lib/eal/include/rte_trace_point_register.h:26:35: note: expanded from macro 'RTE_TRACE_POINT_ARGS_1'
26 | #define RTE_TRACE_POINT_ARGS_1(a) __rte_unused a
| ^~~~~~~~~~~~
../lib/eal/include/rte_common.h:248:37: note: expanded from macro '__rte_unused'
248 | #define __rte_unused __attribute__((__unused__))
| ^~~~~~~~~~
1 error generated.
ninja: build stopped: subcommand failed.
==== End log output ====
Fedora Linux 43
Kernel: 5.4
Compiler: clang gcc (GCC) 15.2.1 20251211 (Red Hat 15.2.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34851/
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:[~2026-01-11 21:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251222004446.62076-1-stephen@networkplumber.org>
2025-12-22 0:43 ` |SUCCESS| pw159399 [RFC] net/virtio: avoid global variable name conflicts checkpatch
2025-12-22 1:42 ` 0-day Robot
2025-12-22 1:42 ` 0-day Robot
2025-12-22 2:01 ` qemudev
2025-12-22 2:06 ` qemudev
2026-01-09 13:07 ` |SUCCESS| pw159399 [PATCH] [RFC] net/virtio: avoid global variable n dpdklab
2026-01-09 13:16 ` dpdklab
2026-01-09 13:38 ` dpdklab
2026-01-09 14:09 ` dpdklab
2026-01-09 14:16 ` dpdklab
2026-01-09 14:26 ` dpdklab
2026-01-09 14:26 ` dpdklab
2026-01-09 15:36 ` dpdklab
2026-01-09 17:02 ` |PENDING| " dpdklab
2026-01-09 17:28 ` dpdklab
2026-01-10 2:49 ` |SUCCESS| " dpdklab
2026-01-10 3:26 ` dpdklab
2026-01-10 4:06 ` dpdklab
2026-01-10 4:17 ` dpdklab
2026-01-10 4:33 ` |PENDING| " dpdklab
2026-01-11 5:35 ` |SUCCESS| " dpdklab
2026-01-11 6:01 ` dpdklab
2026-01-11 6:31 ` dpdklab
2026-01-11 10:46 ` dpdklab
2026-01-11 11:18 ` dpdklab
2026-01-11 21:00 ` dpdklab [this message]
2026-01-12 2:32 ` |PENDING| " dpdklab
2026-01-12 16:18 ` |SUCCESS| " 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=69640f7a.050a0220.2fe741.d0a4SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chenbox@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=maxime.coquelin@redhat.com \
--cc=stephen@networkplumber.org \
--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).