<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>5616</bug_id>
          
          <creation_ts>2013-11-29 18:35:31 +0000</creation_ts>
          <short_desc>Hard reset capability</short_desc>
          <delta_ts>2014-04-18 16:11:45 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>10</classification_id>
          <classification>QA/Testing</classification>
          <product>Runtime Testing</product>
          <component>general</component>
          <version>1.6</version>
          <rep_platform>All</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>18 April 2014: Setting documentation flag to &quot;Done&quot;.</status_whiteboard>
          <keywords></keywords>
          <priority>High</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>1.6</target_milestone>
          
          <blocked>1596</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Paul Eggleton">bluelightning</reporter>
          <assigned_to name="Cristian Iorga">cristian.iorga</assigned_to>
          <cc>alexandru.c.georgescu</cc>
    
    <cc>bluelightning</cc>
    
    <cc>dvhart</cc>
    
    <cc>sgw</cc>
    
    <cc>srifenbark</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Done (doc changes complete)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>39157</commentid>
    <comment_count>0</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2013-11-29 18:35:31 +0000</bug_when>
    <thetext>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.)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>39243</commentid>
    <comment_count>1</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2013-12-05 15:37:12 +0000</bug_when>
    <thetext>I have an example of this working in my testrack using conmux and a web power strip.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40967</commentid>
    <comment_count>2</comment_count>
    <who name="Cristian Iorga">cristian.iorga</who>
    <bug_when>2014-03-07 14:23:18 +0000</bug_when>
    <thetext>Work started.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40968</commentid>
    <comment_count>3</comment_count>
    <who name="Cristian Iorga">cristian.iorga</who>
    <bug_when>2014-03-07 14:27:29 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40969</commentid>
    <comment_count>4</comment_count>
    <who name="Cristian Iorga">cristian.iorga</who>
    <bug_when>2014-03-07 14:28:11 +0000</bug_when>
    <thetext>Initial implementation.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>42517</commentid>
    <comment_count>5</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2014-04-10 12:23:41 +0000</bug_when>
    <thetext>In terms of what we&apos;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&apos;m marking this as resolved; we can open up additional bugs to cover further enhancements where needed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>42574</commentid>
    <comment_count>6</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2014-04-10 19:26:55 +0000</bug_when>
    <thetext>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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>42746</commentid>
    <comment_count>7</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2014-04-18 16:11:45 +0000</bug_when>
    <thetext>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 &quot;Done&quot;.

Scott</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>