[LTP] kirk cannot handle env variable correctly

[Li Wang]

On Tue, Sep 16, 2025 at 3:20 PM Andrea Cervesato <andrea.cervesato@suse.com>
wrote:

>
> On 9/16/25 9:19 AM, Andrea Cervesato wrote:
>
> Hi!
> On 9/16/25 6:35 AM, Li Wang wrote:
>
>
> After looking at the ltp.py, it overrides the user-set LTP_TIMEOUT_MUL env
> variable.
> So maybe we need to enable that to config by --env, what do you think?
>
> Indeed, this is a feature that doesn't make much sense anymore. We should
> fetch env variables from the command line and not from the --env option.
> This was added when Framework API was a plugin and we could implement
> multiple frameworks, but now we only support LTP.
>
> I'm currently working on a new kirk version, where multiple communication
> channels and SUT can be implemented separately in order to create complex
> scenarios. My idea is to remove Framework API and --env variable next to
> that. For now we can merge this patch.
>
> - Andrea
>
> I forgot one thing: can you please send a PR? So I can merge it via github
> and we keep track of it in the next release. Thanks!
>

Yes, this could be a simple workaround:
https://github.com/linux-test-project/kirk/pull/70


-- 
Regards,
Li Wang