On 7 November 2011 09:57, Zygmunt Krynicki <zygmunt.kryni...@linaro.org> wrote:
> W dniu 04.11.2011 15:35, David Gilbert pisze:
>>
>> Hi,
>> I've got a pthread test that is the fall out of a bug fix which is a
>> good test
>> of kernel and libc and would like to add it into Lava.
>>
>> I'm told that I currently have to pick a hardware pack and image - but
>> for
>> this case what I really want to do is to create a test that can be used
>> as a regression test that gets run on whatever the latest kernel is on
>> any of a set of platforms (basically anything of Panda speed or
>> similar/faster).
>
> LAVA is happy to run your test on any hardware pack and root fs you want.
> The first step is to make your test visible to the stack. To do that you
> should wrap it with our lava-test framework. If your test can be compiled to
> a simple executable and invoked to check for correctness then wrapping it
> should be easy as pie. Look at LAVA test documentation lava:
> http://lava-test.readthedocs.org/en/latest/index.html (and report back on
> missing pieces).
>
> The next step is to determine when your test should run. I think that there
> is nothing wrong with simply running it daily on all the hardware packs.
Hi,
Thanks for the response.
My question was started off by reading some notes from ams; in those
the example
has a .json file that has a section that looks like:
{
"command": "deploy_linaro_image",
"parameters":
{
"rootfs": "ROOTFS-URL-HERE",
"hwpack": "HWPACK-URL-HERE"
}
},
Now you say 'I think that there is nothing wrong with simply running
it daily on all
the hardware packs' - what do I change that section to, to indicate that?
(all hw packs is a bit over the top, it would be good to restrict it a
little to save
time, but still, it would be a good start).
I don't see references to that json file in the docs you link to.
Dave
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
