There are two smoke test bugfixes which have come in from our 25.03 DTS development and which should be resolved with this series.
1. The patchseries which we merged for 25.03 which added the testsuite specific configs inadvertently broke enabling smoke tests, as we build the tests config model using the test suite list coming in from the parsed test_run.yaml, before smoke_tests have been added. Then, later in the execution this produces a key error. I think that adding a placeholder smoke tests test suite config is the most reasonable solution to this. Users are unlikely to specify any test config for smoke tests as they don't require any, although if they happen to do so, I understand this change to be non-breaking (and I gave it a test run). 2. I am also seeing the smoke test which relies on regex on dpdk-devbind.py status output is failing on at least one of our systems currently. The fact that this broke is rather peculiar since regex syntax is obviously stable, and my reading of the current regex is that it "should" work. In any case, I simply changed the regex to a pattern which is more permissive and still captures the driver in use, which is what is needed for the testsuite. Patrick Robb (2): dts: include smoke tests in tests config dts: update dpdk-devbind script regex dts/framework/config/test_run.py | 3 +++ dts/tests/TestSuite_smoke_tests.py | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) -- 2.48.1
