Re: Expected errors from make check?

Re: Expected errors from make check?

[Peng Hongbo]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="GB2312", Size: 1945 bytes --]

======= 2005-08-29 17:06:00 from Spirakis, Charles=======

>All --
>
>Seems like there may be a path issue or something with the makefile
>check/test scripts (see below). System is i686 running FC4 using the
>elfutils 114 via SRPMS.
>

After modifying runtest.sh, I found 4 FAILs.

FAIL: ./testsuite/buildok/five.stp
FAIL: ./testsuite/buildok/four.stp
FAIL: ./testsuite/buildok/seven.stp
FAIL: ./testsuite/buildok/six.stp

For four.stp, the detail err log is:
# ./runtest.sh testsuite/buildok/four.stp -v
# cat testsuite/buildok-four.stp.err 
Created temporary directory "/tmp/stapfz7WkA"
Searched '/tmp/systemtap/src/tapset/2.6.11-1.1369_FC4/*.stp', match count 0
Searched '/tmp/systemtap/src/tapset/2.6.11/*.stp', match count 0
Searched '/tmp/systemtap/src/tapset/2.6/*.stp', match count 0
Searched '/tmp/systemtap/src/tapset/*.stp', match count 3
Pass 1: parsed user script and 3 library script(s).
parsed '*' -> func '*'
pattern 'ext3' matches module 'ext3'
focused on module 'ext3' = [cca56000-cca765c9, bias 0]
WARNING: dwfl_module_getdwarf() : relocation refers to undefined symbol
WARNING: no dwarf info found for module ext3
semantic error: no match for probe point
         while: resolving probe point module("ext3").function("*")
Pass 2: analyzed user script.  0 probe(s), 0 function(s), 0 global(s).
Pass 2: analysis failed.  Try again with '-v' (verbose) option.
Running /bin/rm -rf /tmp/stapfz7WkA
# 



--- src/runtest.sh      2005-08-21 20:11:41.000000000 +0800
+++ src.new/runtest.sh  2005-08-30 10:07:47.000000000 +0800
@@ -6,8 +6,8 @@ if [ ! -d testsuite ]; then
   mkdir -p testsuite
 fi
 
-SRCDIR=`dirname $0`
-export SRCDIR
+cd `dirname $0`
+export SRCDIR=${PWD}
 
 SYSTEMTAP_TAPSET=$SRCDIR/tapset
 export SYSTEMTAP_TAPSET




__________________________________________________
Do You Yahoo!?
ÑÅ»¢Ãâ·ÑGÓÊÏ䣭ÖйúµÚÒ»¾øÎÞÀ¬»øÓʼþɧÈų¬´óÓÊÏä
http://cn.mail.yahoo.com/?id=77071

Re: Expected errors from make check?

[Frank Ch. Eigler]

"Peng Hongbo" <penghb2002@yahoo.com.cn> writes:

> [...]
> FAIL: ./testsuite/buildok/five.stp

You need kretprobes in the kernel to build this one.

> FAIL: ./testsuite/buildok/four.stp

Your kernel build may be hitting bugzilla.redhat.com bug#165416.
Has anyone tried a rawhide kernel?  Or if you have access, you 
would have better luck with the RHEL4U2 beta kernel (2.6.9-16.EL).

> FAIL: ./testsuite/buildok/seven.stp
> FAIL: ./testsuite/buildok/six.stp
> [...]

These two reflect known problems: bz#1258 and bz#1257.

- FChE

RE: Expected errors from make check?

[Spirakis, Charles]

Using a similar modification (I used pushd/popd instead of cd), I get the same failures. Interestingly, if I add the -v into the failing scripts, they then are listed as passing...

-- charles

The output of the five.stp without -v (from the command line - same as the make check error):

[cspiraki@cspiraki-lnote src]$ testsuite/buildok/five.stp
Pass 4: compilation failed.  Try again with '-v' (verbose) option.

The output of the five.stp with the -v option (from the command line - make check says success):

[cspiraki@cspiraki-lnote src]$ testsuite/buildok/five.stp
stap: invalid option --
SystemTap translator/driver (version 0.3.1 built 2005-08-29)
Copyright (C) 2005 Red Hat, Inc.
This is free software; see the source for copying conditions.

Usage: stap [options] FILE         Run script in file.
   or: stap [options] -            Run script on stdin.
   or: stap [options] -e SCRIPT    Run given script.

Options:
   --         no more options after this
   -v         verbose [set]
   -h         show help
   -V         show version
   -k         keep temporary directory
   -g         guru mode
   -p NUM     stop after pass NUM 1-5
              (parse, elaborate, translate, compile, run)
   -I DIR     look in DIR for additional .stp script files, in addition to
              /usr/local/share/systemtap/tapset
   -R DIR     look in DIR for runtime, instead of
              /usr/local/share/systemtap/runtime
   -m MODULE  set probe module name, instead of
              stap_500_1125366877
   -o FILE    send output to file instead of stdout
 

> -----Original Message-----
> From: systemtap-owner@sources.redhat.com 
> [mailto:systemtap-owner@sources.redhat.com] On Behalf Of Peng Hongbo
> Sent: Monday, August 29, 2005 6:27 PM
> To: Spirakis, Charles
> Cc: systemtap@sources.redhat.com
> Subject: Re: Expected errors from make check?
> 
> ======= 2005-08-29 17:06:00 from Spirakis, Charles=======
> 
> >All --
> >
> >Seems like there may be a path issue or something with the makefile 
> >check/test scripts (see below). System is i686 running FC4 using the 
> >elfutils 114 via SRPMS.
> >
> 
> After modifying runtest.sh, I found 4 FAILs.
> 
> FAIL: ./testsuite/buildok/five.stp
> FAIL: ./testsuite/buildok/four.stp
> FAIL: ./testsuite/buildok/seven.stp
> FAIL: ./testsuite/buildok/six.stp
> 
> For four.stp, the detail err log is:
> # ./runtest.sh testsuite/buildok/four.stp -v # cat 
> testsuite/buildok-four.stp.err Created temporary directory 
> "/tmp/stapfz7WkA"
> Searched '/tmp/systemtap/src/tapset/2.6.11-1.1369_FC4/*.stp', 
> match count 0 Searched 
> '/tmp/systemtap/src/tapset/2.6.11/*.stp', match count 0 
> Searched '/tmp/systemtap/src/tapset/2.6/*.stp', match count 0 
> Searched '/tmp/systemtap/src/tapset/*.stp', match count 3 
> Pass 1: parsed user script and 3 library script(s).
> parsed '*' -> func '*'
> pattern 'ext3' matches module 'ext3'
> focused on module 'ext3' = [cca56000-cca765c9, bias 0]
> WARNING: dwfl_module_getdwarf() : relocation refers to 
> undefined symbol
> WARNING: no dwarf info found for module ext3 semantic error: 
> no match for probe point
>          while: resolving probe point 
> module("ext3").function("*") Pass 2: analyzed user script.  0 
> probe(s), 0 function(s), 0 global(s).
> Pass 2: analysis failed.  Try again with '-v' (verbose) option.
> Running /bin/rm -rf /tmp/stapfz7WkA
> # 
> 
> 
> 
> --- src/runtest.sh      2005-08-21 20:11:41.000000000 +0800
> +++ src.new/runtest.sh  2005-08-30 10:07:47.000000000 +0800
> @@ -6,8 +6,8 @@ if [ ! -d testsuite ]; then
>    mkdir -p testsuite
>  fi
>  
> -SRCDIR=`dirname $0`
> -export SRCDIR
> +cd `dirname $0`
> +export SRCDIR=${PWD}
>  
>  SYSTEMTAP_TAPSET=$SRCDIR/tapset
>  export SYSTEMTAP_TAPSET
> 
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> 雅虎免费G邮箱－中国第一绝无垃圾邮件骚扰超大邮箱
> http://cn.mail.yahoo.com/?id=77071
> 
> 

Re: Expected errors from make check?

[Frank Ch. Eigler]

charles.spirakis wrote:

> Seems like there may be a path issue or something with the makefile
> check/test scripts (see below). [...]
> [... make check ...]
> FAIL: ./testsuite/buildok/eight.stp
> [and so on]

I have seen this occur when the systemtap build tree was configured
with a relative rather than absolute source directory.  Those relative
directories get sent into the kernel object Makefile in /tmp/stapFOO.
These in turn "stop making sense" with the "make -C /lib/modules/...."
invocation.  This may be fixable in the src/Makefile.am or
src/runtest.sh files, by somehow absolutifying the SYSTEMTAP_RUNTIME
environment variable.

The easiest workaround is to use an absolute source directory when
configuring/building systemtap.

- FChE

Expected errors from make check?

[Spirakis, Charles]

All --

Seems like there may be a path issue or something with the makefile
check/test scripts (see below). System is i686 running FC4 using the
elfutils 114 via SRPMS.

-- charles

[root@cspiraki-lnote src]# rpm -qa | grep kernel
kernel-devel-2.6.12-1.1447_FC4
kernel-2.6.12-1.1447_FC4
kernel-debuginfo-2.6.12-1.1447_FC4

[root@cspiraki-lnote src]# make check
...
FAIL: ./testsuite/buildok/eight.stp
FAIL: ./testsuite/buildok/eleven.stp
FAIL: ./testsuite/buildok/fifteen.stp
FAIL: ./testsuite/buildok/five.stp
FAIL: ./testsuite/buildok/four.stp
FAIL: ./testsuite/buildok/fourteen.stp
PASS: ./testsuite/buildok/nine.stp
FAIL: ./testsuite/buildok/one.stp
FAIL: ./testsuite/buildok/seven.stp
FAIL: ./testsuite/buildok/six.stp
FAIL: ./testsuite/buildok/sixteen.stp
FAIL: ./testsuite/buildok/ten.stp
FAIL: ./testsuite/buildok/thirteen.stp
FAIL: ./testsuite/buildok/three.stp
FAIL: ./testsuite/buildok/twelve.stp
FAIL: ./testsuite/buildok/two.stp
...
=============================================
15 of 93 tests failed
Please report to systemtap@sources.redhat.com
=============================================

[root@cspiraki-lnote testsuite]# more buildok-two.stp.err
Pass 4: compilation failed.  Try again with '-v' (verbose) option.

When I modify the .../testsuite/buildok/two.stp to add the -v option and
then run that manually:

[root@cspiraki-lnote src]# testsuite/buildok/two.stp
Created temporary directory "/tmp/stapu78IAg"
Searched '/usr/local/share/systemtap/tapset/2.6.12-1.1447_FC4/*.stp',
match count 0
Searched '/usr/local/share/systemtap/tapset/2.6.12/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/2.6/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/*.stp', match count 3
Pass 1: parsed user script and 3 library script(s).
Pass 2: analyzed user script.  1 probe(s), 10 function(s), 0 global(s).
Pass 3: translated to C into "/tmp/stapu78IAg/stap_0_1125360180.c"
Running /usr/bin/make -C "/lib/modules/2.6.12-1.1447_FC4/build"
M="/tmp/stapu78IAg" modules
make: Entering directory `/usr/src/kernels/2.6.12-1.1447_FC4-i686'
  CC [M]  /tmp/stapu78IAg/stap_0_1125360180.o
  Building modules, stage 2.
  MODPOST
  CC      /tmp/stapu78IAg/stap_0_1125360180.mod.o
  LD [M]  /tmp/stapu78IAg/stap_0_1125360180.ko
make: Leaving directory `/usr/src/kernels/2.6.12-1.1447_FC4-i686'
Pass 4: compiled into "stap_0_1125360180.ko"
Running /bin/rm -rf /tmp/stapu78IAg