This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Availability of Build and Test System
- From: David Smith <dsmith at redhat dot com>
- To: Elena Zannoni <elena dot zannoni at oracle dot com>
- Cc: systemtap at sourceware dot org, Kris Van Hees <kris dot van dot hees at oracle dot com>, Wenji Huang <wenji dot huang at oracle dot com>
- Date: Thu, 14 Jun 2007 16:13:04 -0500
- Subject: Re: Availability of Build and Test System
- References: <46717636.2080507@oracle.com>
Elena Zannoni wrote:
In the hope that the Sytemtap team finds this useful,
Wenji and Kris have added Systemtap to the projects that are tested
nightly on
some machines we have here at Oracle. The results are published on this
website:
http://build.alchar.org/~aedil/rep/
I took a look at the systemtap results from here:
<http://build.alchar.org/~aedil/rep/ca-tools4/systemtap_fresh.20070614-082235.html>
Several notes:
- This is an output of "make check", not "make installcheck". "make
check" just performs basic sanity checks, and never actually runs any
probes. For this system to be useful for systemtap, it is going to need
to run "make installcheck".
- When either "make check" or "make installcheck" is run, 2 output files
are produced: systemtap.sum and systemtap.log. systemtap.sum contains
basic pass/fail information and systemtap.log contains the full output
needed for debugging. The build log file
(<http://build.alchar.org/~aedil/rep/ca-tools4/dl/systemtap_fresh.20070614-082235.log.bz2>)
only contains systemtap.sum information. To debug most failures, we'll
also need the systemtap.log information.
- From looking at the information that is there in the build log, I'd
guess the test system doesn't have all the needed packages to run
systemtap. Be sure that kernel-devel, kernel-debuginfo, and
kernel-debuginfo-common are installed.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)