[DPDK/DTS Bug 1598] Potential Implementation Problems With Certain conf.yaml attributes within DTS Framework

[DPDK/DTS Bug 1598] Potential Implementation Problems With Certain conf.yaml attributes within DTS Framework

[bugzilla]

[-- 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 --]