[LTP] [PATCH 1/1] kirk: Update to v3.2

[Andrea Cervesato]

Hi!

On Thu Jan 15, 2026 at 9:08 AM CET, Li Wang wrote:
> Hi Andrea,
>
> A quick question on '--framework' changes in v3.2, since before we
> use Kirk with set 'ltp:root' to find the correct LTP installation path.
>   `kirk --framework ltp:root=${LTPDIR} --run-suite $RUNTEST -v
> --json-report $OUTPUTDIR/$RUNTEST.json`
>
> Aafter removing that --framework, I get an error when trying to use
> --env for the installation path.
>   `kirk  --evn LTPROOT=${LTPDIR} --run-suite $RUNTEST -v --json-report
> $OUTPUTDIR/$RUNTEST.json`
>
> ===== Log =====
> # ./kirk --env LTPROOT=/root/ltp-install/  --run-suite sched -v
> --json-report sched.json
> Host information
>
> Hostname:   dell-per430-09.gsslab.pek2.redhat.com
> Python:     3.12.12 (main, Jan  6 2026, 00:00:00) [GCC 14.3.1 20250617
> (Red Hat 14.3.1-2)]
> Directory:  /tmp/kirk.root/tmp1a062qkt
>
> Connecting to SUT: default
> Error: LTP folder doesn't exist: /opt/ltp
>
> Disconnecting from SUT: default
> Session stopped
>
> ==============
>

This is strange. The --env feature is taking info from shell and
updating its dictionary if it has been defined.

This is exactly why this ticket has been open. Too much confusion
between shell variables and --env parameter. We can't have 2 different
ways to set internal variables.

https://github.com/linux-test-project/kirk/issues/72

> But once I put the LTPROOT=${LTPDIR} env separately, it works well:
>   `LTPROOT=/root/ltp-install/  ./kirk  --run-suite sched -v
> --json-report sched.json`
>
> Did I miss something here, or is it a Kirk issue that should be fixed?


Please use this method that is more consistent, also for CI.

Thanks,
-- 
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com