twister: --device-testing always implies --filter runnable

--device-testing implies runnable tests, this was the case before the
rework and was missed in one spot, so instead do that directly in the
argument parser.

Fixes #80428

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif 2024-10-25 09:34:24 -04:00 committed by Henrik Brix Andersen
parent 7b701a40d5
commit 625246f241
2 changed files with 1 additions and 4 deletions

View file

@ -382,7 +382,7 @@ structure in the main Zephyr tree: boards/<vendor>/<board_name>/""")
parser.add_argument(
"--filter", choices=['buildable', 'runnable'],
default='buildable',
default='runnable' if "--device-testing" in sys.argv else 'buildable',
help="""Filter tests to be built and executed. By default everything is
built and if a test is runnable (emulation or a connected device), it
is run. This option allows for example to only build tests that can

View file

@ -644,9 +644,6 @@ class TestPlan:
if ts.get("run_id"):
instance.run_id = ts.get("run_id")
if self.options.device_testing:
self.options.filter = 'runnable'
instance.run = instance.check_runnable(
self.options,
self.hwm