This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
stap make all check test failures
- From: Kevin Feliksa <feliksa at us dot ibm dot com>
- To: systemtap at sourceware dot org
- Date: Thu, 20 Jul 2006 10:06:06 -0500
- Subject: stap make all check test failures
I found 4 of 211 tests fail during the "make all check" testing phase of
a SystemTap build from source. Failing tests are:
.... /buildok/process_test.stp
.... /buildok/sched_test.stp
.... /buildok/scsi.stp
.... /buildok/seven.stp
Note that these tests are executed consecutively. More information is
provided below.
Any suggestions? I've seen these tests also fail during earlier source
module builds on FC-5.
Thanks.
Here's some info:
System:
IBM T30 laptop
Fedora core 5 ISO release (updated)
kernel-2.6.17-1.2157_FC5.i686
elfutils-0.122
kernel-devel-2.6.17-1.2157_FC5
kernel-debuginfo-2.6.17-1.2157_FC5
glib2-devel-2.10.3-1
gcc-4.1.1-1.fc5
gcc-c++-4.1.1-1.fc5
systemtap-20060715
From:
.../testresults/buildok-process_test.stp.err
-------------------------------------------------------------
semantic error: no match for probe point
while: resolving probe point process.signal_handle
Pass 2: analysis failed. Try again with more '-v' (verbose) options.
.../testresults/buildok-sched_test.stp.err
-------------------------------------------------------------
semantic error: no match for probe point
while: resolving probe point kernel.inline("pull_task")
semantic error: no match for probe point
while: resolving probe point scheduler.migrate
semantic error: no match for probe point
while: resolving probe point kernel.inline("idle_balance")
semantic error: no match for probe point
while: resolving probe point scheduler.balance
Pass 2: analysis failed. Try again with more '-v' (verbose) options.
.../testresults/buildok-scsi.stp.err
-------------------------------------------------------------
semantic error: no match for probe point
while: resolving probe point
module("*").function("scsi_prep_fn@drivers/scsi/scsi_lib.c")
semantic error: no match for probe point
while: resolving probe point scsi.ioentry
semantic error: no match for probe point
while: resolving probe point
module("*").function("scsi_dispatch_cmd@drivers/scsi/scsi.c")
semantic error: no match for probe point
while: resolving probe point scsi.iodispatching
semantic error: no match for probe point
while: resolving probe point
module("*").function("scsi_done@drivers/scsi/scsi.c")
semantic error: no match for probe point
while: resolving probe point scsi.iodone
semantic error: no match for probe point
while: resolving probe point
module("*").function("scsi_io_completion@drivers/scsi/scsi_lib.c")
semantic error: no match for probe point
while: resolving probe point scsi.iocompleted
Pass 2: analysis failed. Try again with more '-v' (verbose) options.
.../testresults/buildok-seven.stp.err
-------------------------------------------------------------
semantic error: unresolved target-symbol expression: identifier '$type' at
././testsuite/buildok/seven.stp:11:30
semantic error: unresolved target-symbol expression: identifier '$type' at
././testsuite/buildok/seven.stp:11:30
Pass 2: analysis failed. Try again with more '-v' (verbose) options.