bartoszek/zephyr
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

twister: Bring back scope selection rule using platform_allow

Browse Source 
A change to the scope selection rules was introduced by #52715
but it doesn't comply with the description in the code. What's more,
the change introduces major issues i.e. non deterministic scope
selection, especially in a CI environment. More context at #57595

Signed-off-by: Maciej Perkowski <Maciej.Perkowski@nordicsemi.no>
This commit is contained in:
Maciej Perkowski 2023-05-05 13:34:05 +02:00 committed by Carles Cufí
parent 98858f1e6a
commit 3bf7f83f21
1 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
scripts/pylib/twister/twisterlib/testplan.py
View File

@ -685,10 +685,8 @@ class TestPlan:
b = set(filter(lambda item: item.name in ts.platform_allow, self.platforms))
c = a.intersection(b)
if not c:
_platform_scope = list(filter(lambda item: item.name in ts.platform_allow, \
platform_scope = list(filter(lambda item: item.name in ts.platform_allow, \
self.platforms))
if len(_platform_scope) > 0:
platform_scope = _platform_scope[:1]
# list of instances per testsuite, aka configurations.