Hi all,
I am running LTP tests through LAVA on a Yocto based system. If I run a LTP test suite (like syscalls) by directly calling runltp, LAVA will display it as a single TC, with a single PASS/FAIL verdict.
I think the test definition here solves this problem: https://git.linaro.org/qa/test-definitions.git/tree/automated/linux/ltp/ltp.... But couldn't find a job template that makes use of it. Could you please let me know:
* If this could run on yocto? * Where to find an example job that makes use of this?
Thanks and regards,
Philippe
On Thu, 20 Dec 2018 at 09:39, Philippe Mazet philippe.mazet@nxp.com wrote:
Hi all,
I am running LTP tests through LAVA on a Yocto based system.
If I run a LTP test suite (like syscalls) by directly calling runltp, LAVA will display it as a single TC, with a single PASS/FAIL verdict.
I think the test definition here solves this problem: https://git.linaro.org/qa/test-definitions.git/tree/automated/linux/ltp/ltp....
But couldn’t find a job template that makes use of it.
Could you please let me know:
If this could run on yocto?
probably on yocto based build, but yes, it will work :)
Where to find an example job that makes use of this?
https://lkft.validation.linaro.org/scheduler/job/548744/definition#defline17...
milosz
Thanks and regards,
Philippe
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
---------- The only thing worse than a bug is a bug without any details. The only thing better than a fix is a quick fix.
On 2018年12月20日 17:39, Philippe Mazet wrote:
Hi all,
I am running LTP tests through LAVA on a Yocto based system.
If I run a LTP test suite (like syscalls) by directly calling runltp, LAVA will display it as a single TC, with a single PASS/FAIL verdict.
how many test cases it will be shown in lava report depends on the "pattern" in your test definition, see https://validation.linaro.org/static/docs/v2/writing-tests.html#parsing-comm...
I think the test definition here solves this problem: https://git.linaro.org/qa/test-definitions.git/tree/automated/linux/ltp/ltp....
But couldn’t find a job template that makes use of it.
Could you please let me know:
- If this could run on yocto?
you can't use it directly, obviously, installation dir in yocto is different the one defined here
Where to find an example job that makes use of this?
just update the template to satisfy your case
Lei
Thanks and regards,
Philippe
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Thu, 20 Dec 2018 at 12:29, lei yang lei.yang@windriver.com wrote:
The only thing worse than a bug is a bug without any details. The only thing better than a fix is a quick fix.
On 2018年12月20日 17:39, Philippe Mazet wrote:
Hi all,
I am running LTP tests through LAVA on a Yocto based system.
If I run a LTP test suite (like syscalls) by directly calling runltp, LAVA will display it as a single TC, with a single PASS/FAIL verdict.
how many test cases it will be shown in lava report depends on the "pattern" in your test definition, see https://validation.linaro.org/static/docs/v2/writing-tests.html#parsing-comm...
I think the test definition here solves this problem: https://git.linaro.org/qa/test-definitions.git/tree/automated/linux/ltp/ltp....
But couldn’t find a job template that makes use of it.
Could you please let me know:
If this could run on yocto?
you can't use it directly, obviously, installation dir in yocto is different the one defined here
It's not that obvious to me. Could you explain your reasoning? I'm using this test with OE based built and it works fine. Ultimately you can build it on the target: https://git.linaro.org/qa/test-definitions.git/tree/automated/linux/ltp/ltp....
milosz
Where to find an example job that makes use of this?
just update the template to satisfy your case
Lei
Thanks and regards,
Philippe
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Anyway, in my yocto based image, LTP is deployed on the standard /opt/ltp path. So I could re-use this job example very easily, and it worked perfectly.
Thanks a lot!
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: Thursday, December 20, 2018 1:55 PM To: lei yang lei.yang@windriver.com Cc: Philippe Mazet philippe.mazet@nxp.com; lava-users@lists.lavasoftware.org lava-users@lavasoftware.org Subject: Re: [Lava-users] Best way to run LTP tests on yocto
On Thu, 20 Dec 2018 at 12:29, lei yang lei.yang@windriver.com wrote:
The only thing worse than a bug is a bug without any details. The only thing better than a fix is a quick fix.
On 2018年12月20日 17:39, Philippe Mazet wrote:
Hi all,
I am running LTP tests through LAVA on a Yocto based system.
If I run a LTP test suite (like syscalls) by directly calling runltp, LAVA will display it as a single TC, with a single PASS/FAIL verdict.
how many test cases it will be shown in lava report depends on the "pattern" in your test definition, see https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fval idation.linaro.org%2Fstatic%2Fdocs%2Fv2%2Fwriting-tests.html%23parsing -command-outputs&data=02%7C01%7Cphilippe.mazet%40nxp.com%7C43ec5b6 40ee54d9be42a08d6667a6ae3%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7 C636809073294592358&sdata=FTpKhKejFxO3IxLzWYMIe8Bh1wxqsQlPLIeC9Qf6 Q4U%3D&reserved=0
I think the test definition here solves this problem: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit .linaro.org%2Fqa%2Ftest-definitions.git%2Ftree%2Fautomated%2Flinux%2Fl tp%2Fltp.yaml&data=02%7C01%7Cphilippe.mazet%40nxp.com%7C43ec5b640e e54d9be42a08d6667a6ae3%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C63 6809073294592358&sdata=SAV%2BotDYK46sEvYgGtBLpvw00A3SU4T%2FVpXzZ2h rbzs%3D&reserved=0
But couldn’t find a job template that makes use of it.
Could you please let me know:
If this could run on yocto?
you can't use it directly, obviously, installation dir in yocto is different the one defined here
It's not that obvious to me. Could you explain your reasoning? I'm using this test with OE based built and it works fine. Ultimately you can build it on the target: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.linar...
milosz
Where to find an example job that makes use of this?
just update the template to satisfy your case
Lei
Thanks and regards,
Philippe
Lava-users mailing list Lava-users@lists.lavasoftware.org https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flis ts.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01 %7Cphilippe.mazet%40nxp.com%7C43ec5b640ee54d9be42a08d6667a6ae3%7C686ea 1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636809073294592358&sdata=7Ia 9FGINfEuOw0%2FrUFposeIL6kymiwnuHXQjjA7BrFM%3D&reserved=0
Lava-users mailing list Lava-users@lists.lavasoftware.org https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flis ts.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01 %7Cphilippe.mazet%40nxp.com%7C43ec5b640ee54d9be42a08d6667a6ae3%7C686ea 1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636809073294592358&sdata=7Ia 9FGINfEuOw0%2FrUFposeIL6kymiwnuHXQjjA7BrFM%3D&reserved=0
lava-users@lists.lavasoftware.org
-
lei yang -
Milosz Wasilewski -
Philippe Mazet