Re: [PATCH v1] dts: rename execution to test run

2024-05-02 Thread Luca Vizzarro
Reviewed-by: Luca Vizzarro

Re: [PATCH v1] dts: rename execution to test run

2024-04-30 Thread Jeremy Spewock
+1 for the new name, "execution" in the scope of the config file gets very confusing when people start talking about their individual runs or "executions" of the dts runner. I think test runs will serve as a much more specific name. Reviewed-by: Jeremy Spewock

Re: [PATCH v1] dts: rename execution to test run

2024-04-23 Thread Juraj Linkeš
On Tue, Apr 23, 2024 at 12:58 PM Luca Vizzarro wrote: > > Hi Juraj! > > I am not fussed about naming but I am certainly in favour of making > things less confusing, so I am happy with this change. > Yes, using execution in this context is very confusing. The main thing with this patch is to find

Re: [PATCH v1] dts: rename execution to test run

2024-04-23 Thread Luca Vizzarro
Hi Juraj! I am not fussed about naming but I am certainly in favour of making things less confusing, so I am happy with this change. On 19/04/2024 09:51, Juraj Linkeš wrote: @staticmethod def from_dict( -d: ExecutionConfigDict, +d: TestRunConfigDict, node

[PATCH v1] dts: rename execution to test run

2024-04-19 Thread Juraj Linkeš
The configuration containing the combination of: 1. what testbed to use, 2. which tests to run, 3. and what build targets to test is called an execution. This is confusing since we're using the exact same term to describe other things and execution does not really capture that well the three items