On 12 September 2017 at 09:25, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:58 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:50, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi Neil,
Thanks for your reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:16 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:10, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Robert, Neil:
I managed to prepare a 2017.7 environment. The boot action still works fine. The test action still fails, but in a more 'sane' way I would say. There are strange things like 'None', no lava-test-runner, etc.. Please check the log attached.
You haven't specified a deploy step, so there is no test shell created. Boot just does the boot - to deploy the test environment there must be a deploy action.
As far as I understand, the deployment action occurs before the boot action and consists of preparing a kernel/filesystem in some media (e.g.: as a network filesystem). Ref: https://validation.linaro.org/static/docs/v2/actions-deploy.html
For now, I wanted to run my tests with the kernel and filesystem that is already installed on the Flash memory. Is this impossible with LAVA?
Such a system can only be booted, it cannot operate a Lava Test Shell because there is no way to get the test shell onto the device without a deploy.
There is support for primary connections using SSH https://validation.linaro.org/static/docs/v2/dispatcher-design.html#primary-...
See: Problems with simplistic testing in the documentation. https://validation.linaro.org/static/docs/v2/simple-admin.html#problems-with...
Thanks a lot Neil. # I'm not against deployment, I just wanted to prepare the environment step by step.
The primary connection could be a good solution but it looks like I wouldn't be able to use the PDU, or the autologin features from the u-boot action through the serial port. I will implement the deploy action instead.
By the way, when you talk about "test shell" I am assuming that you mean a shell script or binary that is copied into the target filesystem and executed. Is that correct? My filesystem is very minimal: basically busybox using the ash shell.
"test shell" == Lava Test Shell as defined by the test action block. This relies on POSIX behaviour where the automation drives scripts installed onto the system to execute the test operations themselves.
To handle busybox ash compatibility, just set the Operating System as Open Embedded.
actions: - deploy: # ... rest of the deploy os: oe
https://validation.linaro.org/static/docs/v2/actions-deploy.html#index-18
I am checking the requirements here, do you think there will be a problem with that? https://validation.linaro.org/static/docs/v2/pipeline-admin.html https://validation.linaro.org/static/docs/v2/development-intro.html
Thanks Daniel
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Daniel Sangorrin Sent: Monday, September 11, 2017 5:16 PM To: 'Robert Marshall'; 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
> -----Original Message----- > From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Robert Marshall > Sent: Monday, September 11, 2017 4:47 PM > To: 'Lava Users Mailman list' > Subject: Re: [Lava-users] Help running an inline test > > "Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes: > > > Hi Neil, > > > > Thanks for your quick reply. > > > >> -----Original Message----- > >> From: Neil Williams [mailto:neil.williams@linaro.org] > >> Sent: Monday, September 11, 2017 3:23 PM > >> > >> On 11 September 2017 at 07:06, Daniel Sangorrin > >> daniel.sangorrin@toshiba.co.jp wrote: > >> > Hi, > >> > > >> > I have spent a few days learning LAVA with QEMU and the Beagle Bone black. > >> > Now, I'm trying to setup a Renesas iwg20m board but I have some strange > >> > problem. > >> > # I'm using LAVA v2016.12. > >> > >> Updates are available - you should follow the LAVA documentation for > >> the LAVA repositories and upgrade. > >> > >> https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht... > > > > Thanks, I will try with the 2017.9 version then. > > > Daniel > > If you're doing the test within b@d [1] you should look at my > https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes > branch which has various fixes for our use of lava 2017-7, once that > branch is merged - soon now! - it should 'just work'
Wow Robert, just in time! Thanks.
Daniel
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/