Bug 313511

Summary: [hts5.1.1][ppc64][memory][EL4] - Memory testing giving traceback error
Product: Red Hat Hardware Certification Program Reporter: Satyabrata Maitra <smaitra>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED INSUFFICIENT_DATA QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 5CC: desktop-bugs, llim
Target Milestone: ---   
Target Release: ---   
Hardware: ppc64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-12 16:09:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
Traceback-memory
none
.tar file - contains all .xml files, run-log file and .rpm file for ppc64 hts testing none

Description Satyabrata Maitra 2007-10-01 05:32:29 UTC
Description of problem:
Mrmory testing for ppc64 system giving traceback error.
O.S - EL4-AS-U6
Tree used : 20070927.0

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

How reproducible:
Did once only! And reproduced

Steps to Reproduce:
1. Follow the hts testing procedure and plans for ppc64 system
2. Perform the memory testing with the command :- hts certify --test memory
3. Observe the result in gnome-terminal.
  
Actual results:
Showing Traceback error in g-t

Expected results:
Should not show traceback.

Additional info:
All the error file and other files for this arch are attached here.

Comment 1 Satyabrata Maitra 2007-10-01 05:32:29 UTC
Created attachment 212081 [details]
Traceback-memory

Comment 2 Satyabrata Maitra 2007-10-01 05:33:27 UTC
Created attachment 212091 [details]
.tar file - contains all .xml files, run-log file and .rpm file for ppc64 hts testing

Comment 3 Greg Nichols 2007-12-07 18:38:49 UTC
The problem seems to be in the compilation of threadedmemtest.c - the -m64 CFLAG
causes compilation to fail due to library incompatabilities.

Comment 4 Greg Nichols 2008-03-07 02:28:33 UTC
Please re-test.  I suspect it's a system configuration issue.