On Tue, 19 Jun 2018 at 13:27, Tim Jaacks <tim.jaacks@garz-fricke.com> wrote:

Hello everyone,

I have two cases in which I need to reboot my device during tests:

Depends entirely on the deployment/boot method used by the device.

Does the device-type support BMC?

Exactly which device-types are you wanting to use for this? If any of these are not merged upstream, please attach the full device-type Jinja2 template in the reply.

1. Reboot is active part of the test (e.g. store some persistent settings, reboot, check if persistent settings are correctly loaded after reboot)

Lava Test Shell is not re-entrant. A separate test shell action will be required - *unless* this is an LXC test job where the test shell occurs in the LXC and the LXC has a way to do the reboot, e.g. a fastboot device.

2. Reboot is triggered and has to be evaluated (e.g. activate watchdog, stop resetting it, wait, check if system reboots automatically)

Triggered - how?

How can I hadle these two cases in LAVA?

At the moment, all boot actions need to be defined in the test job in advance and then managed by LAVA. Even with that, some device-types do not successfully get back to a usable point.

Mit freundlichen Grüßen / Best regards

Tim Jaacks
DEVELOPMENT ENGINEER
Garz & Fricke GmbH

Tempowerkring 2
21079 Hamburg

Direct: +49 40 791 899 - 55
Fax: +49 40 791899 - 39
tim.jaacks@garz-fricke.com
www.garz-fricke.com

SOLUTIONS THAT COMPLETE!

Sitz der Gesellschaft: D-21079 Hamburg
Registergericht: Amtsgericht Hamburg, HRB 60514
Geschäftsführer: Matthias Fricke, Manfred Garz

_______________________________________________
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/