Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 510192

Summary: time-record-tt: Fix ltrace testsuite, or ltrace itself
Product: Red Hat Enterprise Linux 5 Reporter: Michal Nowak <mnowak>
Component: ltraceAssignee: Petr Machata <pmachata>
Status: CLOSED WONTFIX QA Contact: BaseOS QE <qe-baseos-auto>
Severity: low Docs Contact:
Priority: low    
Version: 5.3CC: law, mnewsome, ohudlick
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-13 15:06:03 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:
Attachments:
Description Flags
Fix for this issue none

Description Michal Nowak 2009-07-08 09:42:29 UTC
Description of problem:

ltrace testsuite sometimes fails when performing test `time-record-tt`:

[...]
Running ./ltrace.minor/time-record-tt.exp ...
FAIL: Start at 91, End at 91, but PUT call nanosleep(50)!

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

ltrace-0.5-13.45svn.el5

How reproducible:

frequently
  
Actual results:

FAIL: Start at 91, End at 91, but PUT call nanosleep(50)!

or similar

Expected results:

"PASS"

Additional info:

Full log: http://rhts.redhat.com/testlogs/70207/222716/1822165/TESTOUT.log

According to:

https://errata.devel.redhat.com/errata/show/7912#c17 the problem might be the testsuite or possibly ltrace itself.

Comment 3 RHEL Program Management 2010-08-09 19:07:03 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 4 Petr Machata 2012-10-01 16:30:45 UTC
Created attachment 619875 [details]
Fix for this issue

This is upstream patch which should fix this issue.  Porting this, if necessary at all, should be trivial.

Comment 6 Jeff Law 2013-11-13 15:06:03 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being
addressed in Red Hat Enterprise Linux 5, and therefore will be closed.
If this bug is critical to production systems, please contact your Red
Hat support representative and provide sufficient business
justification.