From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1598] Potential Implementation Problems With Certain conf.yaml attributes within DTS Framework
Date: Thu, 12 Dec 2024 19:57:36 +0000 [thread overview]
Message-ID: <bug-1598-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1598
Bug ID: 1598
Summary: Potential Implementation Problems With Certain
conf.yaml attributes within DTS Framework
Product: DPDK
Version: 25.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: npratte@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
Certain conf.yaml attributes, such as 'tarball' under 'dpdk_location' and
'test_suites' under 'test_runs', behave in such a way that, if such attributes
are specified via command line, a conflict of interest arises where the
attribute entered within the conf.yaml take precedent over anything entered in
the command line. Alternatively, if either attribute is not present at all in
the conf.yaml, but either a tarball or at least one test suite is present in
command line arguments, the framework claims that such attributes were not
provided, and the execution is not run at all.
This issue was already partially addressed for the 'test_suites' attribute in
an older implementation for the config changes patch
(https://bugs.dpdk.org/show_bug.cgi?id=1360), but given that this has extended
to other attributes, I've decided to create a separate ticket be made and
perhaps a discussion be had on how we handle cases like this going forward.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3729 bytes --]
reply other threads:[~2024-12-12 19:57 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-1598-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).