[Trac #109] "Preferred Register Settings" compliance testing (PRS)

[Zarro Boogs per Child]

#109: "Preferred Register Settings" compliance testing (PRS)
----------------------------+-----------------------------------------------
 Reporter:  marcelo         |        Owner:  cjb
     Type:  task            |       Status:  new
 Priority:  high            |    Milestone:     
Component:  infrastructure  |   Resolution:     
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by cjb):

  * owner:  rminnich => cjb

Comment:

 Replying to [comment:3 jg]:
 > Now here's the question: can we automate this testing in our process
 somehow, so that this check gets done in our tinderbox?  And if it fails,
 the tinderbox is marked as burning?

 In principle, absolutely -- running commands on the board and inspecting
 their output is already being done.  However, the build image presumably
 doesn't ship with tcl by default, so we'd have to install it somehow.  We
 can't use an RPM unless we want to limit ourselves to only testing the
 "development" build, so we'd have to have a tcl build kept on the
 tinderbox machine and copied over to the board each time.

 Reassigning to myself to get tcl and the PRS script into the tinderbox,
 since it looks like the rest of the bug's been completed.

-- 
Ticket URL: <http://dev.laptop.org/ticket/109#comment:4>
One Laptop Per Child <http://laptop.org/>