Results of tests on nightly builds

Results of tests on nightly builds

[William Cohen]

I have a cron job set up on a number of machines to run the systemtap 
tests each night to see how things are working (or broken). Here are the 
results of the tests.

-Will

Summarize the results of nightly test run Feb 1 2006.

The pmap_agg_overflow tests requires smp machines so on the single
processor machines it ends up being unsupported.


FC4 i686 UP Linux 2.6.14-1.1656_FC4

buildok-six.stp: unable to resolve kernel.inline("context_switch") on
	Linux 2.6.14-1.1656_FC4

		=== systemtap Summary ===

# of expected passes		127
# of unsupported tests		1


FC5 i686 SMP Linux 2.6.15-1.1884_FC5smp

buildok-seven.stp: unable to find indentifiers $type and $task

Testsuite summary of failed tests
FAIL: ./systemtap.maps/ix_hist.stp timed out (PASSED when run by hand??!)
FAIL: profile (timeout) (looks like dependent times out because of jiffies)
FAIL: profile
		=== systemtap Summary ===

# of expected passes		126
# of unexpected failures	3




FC5 x86_64 SMP Linux 2.6.15-1.1884_FC5 (1 processor in machine)

buildok-seven.stp can't resolve identifer '$task' in buildok/seven.stp:19:35

	=== systemtap Summary ===

# of expected passes		127
# of unsupported tests		1



RHEL4U3 i686 SMP Linux 2.6.9-27.ELsmp (1 processor in machine)

		=== systemtap Summary ===

# of expected passes		127
# of unsupported tests		1



RHEL4U3 x86_64 SMP Linux 2.6.9-27.ELsmp

Looks like there is a problem with the debug information. However,
most all of the tests run it is just one semok test and one run test
that fail due to problems with debuginfo.

semok-twenty.stp very strange couldn't find debuginfo all other tests worked
semantic error: cannot find module stap_18875 debuginfo: No such file or 
directory


Testsuite summary of failed tests
FAIL: ./systemtap.stress/current.stp startup (eof)
semantic error: cannot find module stap_18875 debuginfo: No such file or 
directory

		=== systemtap Summary ===

# of expected passes		125
# of unexpected failures	1

Re: Results of tests on nightly builds

[Frank Ch. Eigler]

wcohen wrote:

> [...]
> semok-twenty.stp very strange couldn't find debuginfo [...]
> semantic error: cannot find module stap_18875 debuginfo: No such file
> or directory

This indicates that there was already a systemtap probe left running
when the next one came along.  Since semok/twenty.stp attempts to
enumerate "kernel.module("*")", the prior systemtap module is also
selected for analysis.  elfutils couldn't find its debug information,
since it is only to be found under /tmp/ someplace.

- FChE