This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Debian 6 test suite results


On 07/31/2013 06:30 PM, Yichun Zhang (agentzh) wrote:
> Hello!
> 
> I'd like to share systemtap's test suite results on our Debian 6
> x86_64 system (with kernel 3.10.1 compiled by ourselves):
> 
> kernel version: 3.10.1
> systemtap version: version 2.4/0.148, commit release-2.3-15-g0ba56fe
> 
>                 === systemtap Summary ===
> 
> # of expected passes            2831
> # of unexpected failures        76
> # of unexpected successes       1
> # of expected failures          283
> # of unknown successes          1
> # of known failures             41
> # of untested testcases         95
> # of unsupported tests          4
> 
> Below are all the test failures:

I looked at several of these. There are 2 major things going on:

- systemtap can't find module debuginfo
- systemtap can't seem to parse the output of `uname -i`


> Running ./systemtap.base/bz6503.exp ...
> FAIL: bz6503 0 0

The bz6503 failure happened because systemtap couldn't find the module
debuginfo.

> Running ./systemtap.base/cmd_parse.exp ...
> FAIL: cmd_parse15: eof
> FAIL: cmd_parse16: eof

There is something odd going on with your kernel/system. 'uname -i'
isn't returning anything the testsuite recognizes, which leads to the
following:

Makefile:579: /lib/modules/3.10.1-trace+/build/arch/unknown/Makefile: No
such file or directory


> Running ./systemtap.base/ipaddr.exp ...
> FAIL: ipaddr_IPv4_recvmsg shutdown (eof)
> --

The ipaddr.exp failure is also weird. The test script runs 'nc' to
generate some network traffic, but none is seen. Once again systemtap
complains that it can't find the "sunrpc" or "nfs" module debuginfo.

Does your kernel have those configured in?

> Running ./systemtap.base/preprocessor.exp ...
> FAIL: preprocessor basic ops
> --

The preprocessor.exp is a result of another failure to understand your
kernel architecture.

> Running ./systemtap.context/fib.exp ...
> FAIL: fib (4 1)
> FAIL: fib (670 1)

The fib.exp failure is probably PR15783.

> Running ./systemtap.pass1-4/buildok.exp ...
> FAIL: buildok/fortysix.stp
> FAIL: buildok/memory-detailed.stp
> FAIL: buildok/networking-detailed.stp
> FAIL: buildok/nfs-all-probes.stp
> FAIL: buildok/nfs-detailed.stp
> FAIL: buildok/nfs-embedded.stp
> FAIL: buildok/nfs_proc-embedded.stp
> FAIL: buildok/nfsd-all-probes.stp

The nfs errors are related to the fact that stap couldn't find NFS
either compiled into the kernel or as a module.

> FAIL: buildok/pr10678.stp
> FAIL: buildok/rpc-all-probes.stp
> FAIL: buildok/rpc-embedded.stp
> FAIL: buildok/scsi-all-probes.stp
> FAIL: buildok/scsi-detailed.stp
> FAIL: buildok/scsi-embedded.stp

The scsi errors are related to the fact that stap couldn't find SCSI
either compiled into the kernel or as a module.

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]