Bug 506959

Summary: Few minor systemtap-testsuite issues
Product: Red Hat Enterprise Linux 5 Reporter: Petr Muller <pmuller>
Component: systemtapAssignee: Frank Ch. Eigler <fche>
Status: CLOSED ERRATA QA Contact: BaseOS QE <qe-baseos-auto>
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: ebachalo, mjw, 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: 2010-03-30 09:06:09 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:

Description Petr Muller 2009-06-19 14:54:40 UTC
Description of problem:
Few of the testcases in the testsuite have minor issues which generate noise when doing a testsuite run.

1) buildok/thirtyone.stp is not an executable, but it is treated as one when buildok.exp runs. Thus, bogus 'Permission denied' messages appear when running. Similar issue was fixed in the last iteration, but this testcase was brought in with some new fix

2) systemtap.base/sdt.exp has bogus failures when doing simple 'make installcheck', because compilation of std.c fails due to '#include "sdt.h"'. This header is only found when running in the tree, not when running the installcheck.

3) systemtap.base/crash.exp is trying to do 'spawn stap $srcdir/$subdir/testlog.stp', which fails because the file is simply not there:
[root@x86-64-v00 testsuite]# find . -name testlog.stp

Version-Release number of selected component (if applicable):
# rpm -q systemtap-testsuite
systemtap-testsuite-0.9.7-5.el5

How reproducible:
Always

Steps to Reproduce:
1. all three issues manifest when doing 'make installcheck'

Actual results:
bogus failures

Expected results:
tests do their job

Comment 1 Frank Ch. Eigler 2009-12-01 14:59:16 UTC
already fixed upstream

Comment 6 errata-xmlrpc 2010-03-30 09:06:09 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-2010-0308.html