Bug 231974 - Hardware testing -> CORE (pressure test) test fail.
Hardware testing -> CORE (pressure test) test fail.
Status: CLOSED WONTFIX
Product: Red Hat Ready Certification Tests
Classification: Retired
Component: rhr2 (Show other bugs)
2
i386 Linux
medium Severity urgent
: ---
: ---
Assigned To: Greg Nichols
Will Woods
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-13 08:29 EDT by Howard Liang
Modified: 2008-07-17 18:04 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-17 18:04:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
log files (495 bytes, application/octet-stream)
2007-03-13 08:29 EDT, Howard Liang
no flags Details

  None (edit)
Description Howard Liang 2007-03-13 08:29:01 EDT
Description of problem:

CORE (pressure test) fails test.
I checked /var/log/rhr/tests/CORE/output.log and got below message.
"+ automated_CORE
 + '[' -f /dev/null ']'
 276725596587460360056082170067295855173"

Could you teach me how to solve the issue.

Test program: rhr2-2.0-3.EL4.i386.rpm
Comment 1 Howard Liang 2007-03-13 08:29:01 EDT
Created attachment 149918 [details]
log files
Comment 2 Erik C. Dasher 2007-06-26 14:53:04 EDT
This issue reproduces on Intel hardware running RHEL 4.5 AS GA x86_64.  Test
package is rhr2-2.0-3.EL4.x86_64.rpm.  The log file I see is identical.  

Unfortunatly this issue hasn't had any activity or progress for the last three
months, so we will avoid the CORE pressure test until we can obtain better
information.  
Comment 3 Rob Landry 2008-07-17 18:04:23 EDT
rhr2 has been deprecated, closing these remaining bugs as WONTFIX.  Future bugs
against the "hts" test suite should be opened agains the "Red Hat Hardware
Certification Program" product selecting either "Test Suite (harness)" or "Test
Suite (tests)" components.

Note You need to log in before you can comment on or make changes to this bug.