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: Availability of Build and Test System


On Thu, Jun 14, 2007 at 04:13:04PM -0500, David Smith wrote:
> 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".

I most definitely agree.  The choice to run 'make check' for the current
runs is quite deliberate to ensure that the current worker nodes
(executing the builds) are at minimal risk of crashing.  Of course, the
goal is to run the full testsuite.  But that will need a bit of work at
this point, because crashing the worker nodes is a bit of a problem
right now.  It is an important problem to resolve either way, since e.g.
frysk has accomplished a few machine crashes in the past as well.

Part of this will be trying to capture as much data as possible in the
event of a crash.

> - 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.

Adding in the systemtap.log file won't be a problem.  Right now, the
default is to capture the stdout and stderr output in a single stream,
and upload that.  Obviously, for projects that use dejagnu for their
testing framework, the .sum and .log files will need to be included as
well.

> - 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.

That box was indeed missing kernel-devel at the time that build and test
run was executed.  That has since been corrected.

Thanks for the feedback.  Suggestions from anyone on issues with the
system are more than welcome, and of course, contributing bulds by
running a worker node (very lightweight and easy) is always welcome
also.

	Cheers,
	Kris


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