Bug 5616

Summary:	Hard reset capability
Product:	[QA/Testing] Runtime Testing	Reporter:	Paul Eggleton <bluelightning>
Component:	general	Assignee:	Cristian Iorga <cristian.iorga>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	High	CC:	alexandru.c.georgescu, bluelightning, dvhart, sgw, srifenbark
Version:	1.6
Target Milestone:	1.6
Hardware:	All
OS:	Multiple
Whiteboard:	18 April 2014: Setting documentation flag to "Done".
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Done (doc changes complete)
Bug Depends on:
Bug Blocks:	1596

Description Paul Eggleton 2013-11-29 18:35:31 UTC

Add the ability to reset the hardware under test automatically. This really requires hardware assistance in the form of a web/serial controlled power strip, and there is no standard protocol for interacting with these although conmux does 
abstract this to a degree. To keep this simple, we would just have a variable 
that points to a command/script that does the hard reset, and then that can be 
defined outside of the build system. (We probably ought to be using conmux in our QA setups however.)

Comment 1 Darren Hart 2013-12-05 15:37:12 UTC

I have an example of this working in my testrack using conmux and a web power strip.

Comment 2 Cristian Iorga 2014-03-07 14:23:18 UTC

Work started.

Comment 3 Cristian Iorga 2014-03-07 14:27:29 UTC

A first solution built around the current local lab setup was developed, involving the local infrastructure (Romania).
This proof of concept allows people involved in AHWT feature to test the implementation using an existing lab infrastructure and setup.

The current setup and infrastructure involves boards connected to a remote powerstrip, which can be controlled programatically via an expect script that is integrated in build/test environment.

Connections are made via SSH/HTTP.

Comment 4 Cristian Iorga 2014-03-07 14:28:11 UTC

Initial implementation.

Comment 5 Paul Eggleton 2014-04-10 12:23:41 UTC

In terms of what we'll deliver for 1.6, this is now complete as of this commit:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=397225996446ac91c5623972f2ca5c8b3a17c31e

I'm marking this as resolved; we can open up additional bugs to cover further enhancements where needed.

Comment 6 Scott Rifenbark 2014-04-10 19:26:55 UTC

Hi, 

The documentation part of this bug is tied up with bug 5554.  Aside from the review links I have placed in that bug, see http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#hardware-image-enabling-tests for a description.  

That link could use a review in light of this bug here.  Adding Paul to the bug CC list.

Thanks, 
Scott

Comment 7 Scott Rifenbark 2014-04-18 16:11:45 UTC

Hi, 

I worked with Stefan here to update the section on running tests.  We are good now with it all.  See http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#performing-automated-runtime-testing.

Setting the doc flag to "Done".

Scott