Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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
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
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