On 31 July 2014 14:44, Ryan Harkin <ryan.harkin(a)linaro.org> wrote:
> Hi there,
>
> Do any of you fine people fancy talking to Liam at ARM about how to get a
> new board set up in LAVA and about what he has to do?
>
> You can go direct to him or I can loop you into the email chain if you let
> me know who to put in the firing line ;-)
>
The linaro-validation mailing list is the best place: Linaro
Validation <linaro-validation(a)lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-validation.
> Hi Ryan, apologies I know you’re probably not the right person, but I’m
> hoping you can put us in contact with the right guy.
... mailing list.
> What I wanted to know (any maybe use TC2 as an example) is what s/w is
> required to me running on a target platform for LAVA to work?
>
> Do you need Linux running, do you need DVFS, power gating supported etc.
LAVA being written by Linaro is heavily based around the Linux kernel,
so a kernel image with a CI loop outside LAVA to build new kernels is
going to be the first thing. DVFS is not required, unless if the test
writer (you) is going to want results relating to DVFS. Similar with
power gating. Hardware wise, a serial connection is absolute - and it
needs to not be interrupted or cause bootloader interference when the
board is hard reset remotely. (LAVA will pull the power without
warning and without using any on-board support from time to time. The
board must react smoothly to these resets.) If all you are doing is
booting a kernel, that is all that LAVA stipulates. To do more complex
testing, some amount of writeable media connectivity, working ethernet
support, a distribution with POSIX compatibility and a command line
shell are going to be useful. LAVA developers don't write the tests
for the boards in LAVA, those will need to be designed and tested by
whoever wants the test results. Everything else that may become
necessary is down to what tests need to run on the board.
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
Hi Lava Team,
Could you please help me out in booting android image on Vayu board which
is deployed recently in LAVA lab.
I have given a sample job to boot android on Vayu board. But, It got failed
due to some errors.
The job is posted @ https://validation.linaro.org/scheduler/job/140102
It would be great if some one helps me out.
--
Thanks and Regards,
HariGopal G
Android Engineer
If you write the test case, LAVA can likely run it. Without seeing the test
case source code, there's no way to be sure what will be needed but most of
the existing tests which people run using LAVA involve some level of
functional testing of computing and storage and there are plenty of
examples which can be viewed and copied from jobs previously run by LAVA.
There's no point asking LAVA for a LAVA test case - LAVA does not provide
or write test cases other than for our own internal development. Those who
want to run tests using LAVA write the tests for LAVA. All LAVA needs is a
path to a YAML file which contains a run step to do something.
https://validation.linaro.org/static/docs/writing-tests.html#writing-tests
On 15 July 2014 02:48, Huangwenhui <huangwenhui(a)hisilicon.com> wrote:
> I have sent a message for help on LAVA official website, We are developing
> IT class chip, used in the field of storage and computing.
>
> Follow-up to do a lot of functional tests on LAVA testing platform for
> computing and storage. So we want to know whether LAVA considered adding
> related-testcase.
>
>
>
>
>
> 发件人: Neil Williams [mailto:neil.williams@linaro.org]
> 发送时间: 2014年7月14日 21:01
> 收件人: Huangwenhui
> 抄送: Zhanweitao; Linaro Validation
> 主题: Re: Ask for LAVA test case
>
> The Linaro Validation mailing list is the best place to ask questions like
> this.
>
> https://validation.linaro.org/static/docs/overview.html
>
> https://validation.linaro.org/static/docs/#lava-test-developer-guide
>
> LAVA does not stipulate any test case design strategy and although LAVA
> developers do write some tests, those are generally for our own use in
> testing the LAVA code. Most tests in LAVA are written by other teams. Tests
> are just shell scripts and can test whatever calls you need to test,
> dependent on the board and the test image in use.
>
> On 14 July 2014 13:57, Huangwenhui <huangwenhui(a)hisilicon.com> wrote:
> Hi,
> I am Huangwenhui. An employee of Huawei Hisilicon Ltd.
>
> We are analyzing your LAVA testcase. We are developing storage-server
> chips.
>
> And what is the LAVA test case design strategy?
>
> Will you add more Server-related test cases?
>
> Expect replies. E-mail: huangwenhui(a)hisilicon.com
>
> Best Regards.
>
> Huangwenhui
>
>
>
>
> --
>
> Neil Williams
> =============
> neil.williams(a)linaro.org
> http://www.linux.codehelp.co.uk/
>
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
The Linaro Validation mailing list is the best place to ask questions like
this.
https://validation.linaro.org/static/docs/overview.htmlhttps://validation.linaro.org/static/docs/#lava-test-developer-guide
LAVA does not stipulate any test case design strategy and although LAVA
developers do write some tests, those are generally for our own use in
testing the LAVA code. Most tests in LAVA are written by other teams. Tests
are just shell scripts and can test whatever calls you need to test,
dependent on the board and the test image in use.
On 14 July 2014 13:57, Huangwenhui <huangwenhui(a)hisilicon.com> wrote:
> Hi,
> I am Huangwenhui. An employee of Huawei Hisilicon Ltd.
>
> We are analyzing your LAVA testcase. We are developing storage-server
> chips.
>
> And what is the LAVA test case design strategy?
>
> Will you add more Server-related test cases?
>
> Expect replies. E-mail: huangwenhui(a)hisilicon.com
>
> Best Regards.
>
> Huangwenhui
>
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
# Progress #
* Fix bug #82 - scheduler.all_device_types returns list of plain device
* Fix bug #61 - XML-RPC interface needs a method to fetch job definition
* Collection of raw materials for home lab expansion
* Home lab expansion with 2 panda boards up (more in queue)
* Arndale board woes!
* LAVA-1299: Boot time metadata
* Code reviews
* Cards - 20%
* bugs - 60%
* home lab expansion - 15%
* code reviews - 5%
# Plan #
* Continue with pending cards and bugs and home lab expansion
--
Senthil Kumaran
http://www.stylesen.org/http://www.sasenthilkumaran.com/
Hi all;
Here is a link to the document containing the summary of the LAVA sprints
held in June.
1 day Mini Sprint (LAVA & LAVA LAB) in Cambridge, UK
3 day LAVA Sprint in Grenoble, FR
The meetings were a great chance to work through some challenging topics
and we look forward to further discussions on these efforts.
[1]
https://docs.google.com/a/linaro.org/document/d/1BqHKESGMENBTsynczUnqq8In5t…
NOTE: To reduce the impact of 'reply-all', I have BCC'd the Linaro
Executives, the LAVA mailing list and the Linaro Techleads. Please feel
free to reply to all, the team welcomes your comments and feedback.
Regards
Alan
--
Alan Bennett, Director of Product Technology
Linaro.org │ Open source software for ARM SoCs | Follow Linaro: Facebook |
Twitter | Blog
irc: akbennett | alan.bennett(a)linaro.org | linaro toolchain, linaro stable
kernel & linaro lava
