Bug 1375

Summary: Make limited use of "per testsuite" conf files.
Product: DPDK Reporter: Patrick Robb (probb)
Component: DTSAssignee: Juraj Linkeš (juraj.linkes)
Status: UNCONFIRMED ---    
Severity: enhancement CC: juraj.linkes, probb
Priority: Low    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   

Description Patrick Robb 2024-01-25 21:00:56 CET 
There will be examples of testsuite which require some divserse input on a per testsuite or environment basis (setting expected baselines for a testsuite in perf testing is one example). So, we are going to be doing this at some point anyways, and I think it is okay to do so now with functional tests too if it can help make testsuites more concise.

I don't want this suggestion to be conflated with our previous discussion about building a YAML schema and intepreter for taking testsuite parameters and also python functions and mapping that to a python testsuite. I think it's clear based on our 1/24 meeting that we are not going in that direction. However, we probably do need per-testsuite conf files for some (but not all) suites. I think how we best leverage this can be a discussion point for next week's DTS meeting.
Comment 1 Patrick Robb 2024-02-01 15:48:26 CET 
There should be one monolithic YAML file, which all testsuites can be configured in. First indentation should be the testsuite, and how values are set should be common across testsuites.
Comment 2 Juraj Linkeš 2024-02-14 14:38:34 CET 
That one monolithic YAML file is under https://bugs.dpdk.org/show_bug.cgi?id=1354 or very closely related to that. We should discuss clearly what we want to configure where and update these tickets accordingly.