From: William Cohen <wcohen@redhat.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Current systemtap testsuite results
Date: Wed, 07 Sep 2005 15:57:00 -0000 [thread overview]
Message-ID: <431F0DCF.5020109@redhat.com> (raw)
I tried out running the testsuite we have checked into the systemtap cvs
on a variety of platforms with the current snapshot of systemtap
(9/7/2005) running on each. The results were the worst on the RHEL4
x86-64 machine. Below are more summaries of passes and fails and some
analsysis on why things failed. The kmodule.stp test fails for
everything because the kernels do not have the required debug
information for the modules.
-Will
RHEL4 x86-64 (calfee)
2.6.9-15.ELsmp
=== systemtap Summary ===
# of expected passes 67
# of unexpected failures 13
FAIL: ./systemtap.base/and.stp startup (eof)
FAIL: ./systemtap.base/kmodule.stp compilation
FAIL: ./systemtap.base/logical_not.stp startup (eof)
FAIL: ./systemtap.base/or.stp startup (eof)
FAIL: ./systemtap.base/simple.stp startup (timeout)
FAIL: ./systemtap.base/subtract.stp startup (timeout)
FAIL: ./systemtap.base/tri.stp startup (timeout)
FAIL: ./systemtap.base/xor.stp startup (timeout)
FAIL: arith
FAIL: primes
FAIL: profile
FAIL: syscalls-count (0)
FAIL: syscalls-run (0)
On RHEL4 x86-64 the and.stp, logical_not.stp, or.stp failed in the same
manner when an attempt to install the module was made. It appears that
the names are not as unique as desired andthat the x86-64 is speeds
enough to end up with the same name for two different tests.
insmod: error inserting '/tmp/staphXBwpp/stap_0_1126103660.ko': -1 File
exists
systemtap.samples/arith.stp and systemtap.samples/profile.stp fail due
to "implicit declaration of function `task_pt_regs'". Looks like the
runtime library is not providing that.
systemtap.samples/syscalls.stp can crash the x86-64 kernel.
It looks like sometime tripped up the dejagnu test harness, so tests
after simple.stp were not installed/running.
RHEL4 i686 (slingshot)
2.6.9-15.ELsmp
=== systemtap Summary ===
# of expected passes 92
# of unexpected failures 1
FAIL: ./systemtap.base/kmodule.stp compilation
FC4 i686 (montague)
2.6.12-1.1447_FC4
=== systemtap Summary ===
# of expected passes 90
# of unexpected failures 3
FAIL: ./systemtap.base/kmodule.stp compilation
FAIL: profile
FAIL: syscalls-run (14)
rawhide (trek)
2.6.13-1.1530_FC5smp
=== systemtap Summary ===
# of expected passes 86
# of unexpected failures 5
FAIL: profile (timeout)
FAIL: profile
FAIL: syscalls-count (13)
FAIL: syscalls-run (timeout)
FAIL: syscalls-run (0)
next reply other threads:[~2005-09-07 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 15:57 William Cohen [this message]
2005-09-07 17:06 ` Frank Ch. Eigler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=431F0DCF.5020109@redhat.com \
--to=wcohen@redhat.com \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).