Bug 83654

Summary: results format need to be integrated with overall process
Product: [Retired] Red Hat Ready Certification Tests Reporter: Kevin Krafthefer <krafthef>
Component: otherAssignee: Rob Landry <rlandry>
Status: CLOSED NEXTRELEASE QA Contact: Rob Landry <rlandry>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.8CC: hcp-admin
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-11-04 22:06:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kevin Krafthefer 2003-02-06 20:02:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
reviewing and posting results is time consuming and error prone. 
(standard package and crush) results should be simple to review. the results for
a device that passes, should create a file that is aimed at simple updating (if
not completely automated) of the HCL. the results for a failed device should
include a failure mode file that is given back to the manufacture. the fail mode
package should contain any system information pertaining to the device in
question and failure mode.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. run test suite
2.
3.
    

Additional info:

Comment 1 Rob Landry 2003-09-29 19:34:52 UTC
rhr2 package format = RPM; while not automatic posting should resolve many
gripes about the old package format; also rhr-crush == CORE in the new suite
being integrated with rhr-kernel and rhr-memory.

Comment 2 Rob Landry 2003-11-04 22:06:00 UTC
process integration is complete from the standpoint of the test suite.
 It will now allow for a replay of the [ OK ]'s and [FAILED]'s which
should allow for quick review.  The bigger step is going to be WRT
updating the HCL and issue tracker.  I'm going to go ahead and close
this as the remainder is not a problem with the test suite.