RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 691760 - systemtap.stress/conversions.exp: 3PASS -> 3FAIL
Summary: systemtap.stress/conversions.exp: 3PASS -> 3FAIL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: systemtap
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Frank Ch. Eigler
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-29 12:16 UTC by Petr Muller
Modified: 2016-09-20 02:07 UTC (History)
3 users (show)

Fixed In Version: systemtap-1.4-6.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 13:55:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
diff between PASSing and FAILing systemtap.log (8.42 KB, text/plain)
2011-03-29 12:16 UTC, Petr Muller
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0651 0 normal SHIPPED_LIVE systemtap bug fix and enhancement update 2011-05-19 09:37:25 UTC

Description Petr Muller 2011-03-29 12:16:50 UTC
Created attachment 488419 [details]
diff between PASSing and FAILing systemtap.log

Description of problem:
The RHEL6.1 candidate systemtap packages has 3 FAILs in
systemtap.stress/conversions.exp testcase, while the 6.0.z systemtap has 3 PASSes here. This happens on i686 and ppc64, unknown on s390x and
x86_64.

Version-Release number of selected component (if applicable):
Environment:
kernel-2.6.32-122.el6
elfutils-0.152-1.el6
systemtap-testsuite-1.4-4.el6

Systemtap:
systemtap-1.2-11.el6_0 PASS
systemtap-1.4-4 FAIL

How reproducible:
always

Steps to Reproduce:
1. cd /usr/share/systemtap/testsuite/
2. make RUNTESTFLAGS=systemtap.stress/conversions.exp installcheck
3.

Actual results:
FAIL

Expected results:
PASS

Additional info:
systemtap.sum:
 Running /usr/share/systemtap/testsuite/systemtap.stress/conversions.exp ...
-PASS: conversions.stp 0
-PASS: conversions.stp 0xffffffff
-PASS: conversions.stp 0xffffffffffffffff
+FAIL: conversions.stp 0 (13)
+FAIL: conversions.stp 0xffffffff (13)
+FAIL: conversions.stp 0xffffffffffffffff (13)

I could not extract any useful snippet from systemtap.log, so I will attach diff between PASSing and FAILing systemtap.log

Comment 2 William Cohen 2011-03-29 16:38:45 UTC
This has been fixed in the upstream systemtap with the following patch:

http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=c1863f2c7be024ee5acb87ae0e5e834183a90b8e

Comment 3 Frank Ch. Eigler 2011-04-06 14:36:46 UTC
Small testsuite fix, patch in hand.

Comment 7 errata-xmlrpc 2011-05-19 13:55:05 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0651.html


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