From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1803] DTS logs lose verbosity with addition of new IntEnum
Date: Thu, 16 Oct 2025 13:09:16 +0000 [thread overview]
Message-ID: <bug-1803-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1803
Bug ID: 1803
Summary: DTS logs lose verbosity with addition of new IntEnum
Product: DPDK
Version: unspecified
Hardware: All
URL: http://patchwork.dpdk.org/project/dpdk/patch/202509231
03758.3192015-2-paul.szczepanek@arm.com/
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: abailey@iol.unh.edu
CC: juraj.linkes@pantheon.tech, paul.szczepanek@arm.com,
probb@iol.unh.edu
Target Milestone: ---
When DTS is run, the logs used to output the name of a NIC capability when a
test was skipped due to it missing said capability. The logs now output the
integer representation of the flag in the logs instead of the name of the
capability.
For Example: "reason: Required capability '{82}' not found."
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-10-16 13:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1803-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).