RE: what if I wanted to write some tests...

["Chen, Brad" <brad dot chen at intel dot com>]

> Of course - you can check out the translator and/or runtime sources.
> The former has various self-tests ("make check"); the latter has
> various kprobes-flavoured test programs.

Indeed; I had tried to work from runtime/tests but 
get a bunch of syntax errors. I was hoping somebody
could confirm that this was supposed to work, and
take a guess at what I might have wrong. I just did 
a "recreate_links" from ../user; doesn't help. See
test output below.

It seems I am able to ./build in runtime/probes,
so perhaps I'll work there for a while and try 
runtime/tests later.

I don't want to complain but, in trying to run the
where_func probe:
- name of .ko has changed
- nothing to indicate you should use the ./stp script
  in the directory
- ./stp lsmod assumes /sbin in path
and I still haven't gotten it running yet. So if anybody
has hints let me know, and please let me know if you own
this directory and wouldn't mind me me updating things a 
bit when I get them figured out.

Brad

========================================================================
=

tclsh all.tcl
Running all SystemTap tests
Tests running in interp:  /usr/bin/tclsh
Tests located in:  /home/bchen/proj/systemtap/cvs/src/runtime/tests
Tests running in:  /home/bchen/proj/systemtap/cvs/src/runtime/tests
Temporary files stored in
/home/bchen/proj/systemtap/cvs/src/runtime/tests
Test files run in separate interpreters
Running tests that match:  *
Skipping test files that match:  l.*.test
Only running test files that match:  *.test
Tests began at Mon Jun 20 01:34:08 PM PDT 2005

Tests ended at Mon Jun 20 01:34:08 PM PDT 2005
all.tcl:        Total   0       Passed  0       Skipped 0       Failed
0
Sourced 0 Test Files.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
maps test began at Mon Jun 20 01:34:08 PM PDT 2005

Tests running in interp:  /usr/bin/tclsh
Tests located in:  /home/bchen/proj/systemtap/cvs/src/runtime/tests/maps
Tests running in:  /home/bchen/proj/systemtap/cvs/src/runtime/tests
Temporary files stored in
/home/bchen/proj/systemtap/cvs/src/runtime/tests
Test files run in separate interpreters
Running tests that match:  *
Skipping test files that match:  l.*.test
Only running test files that match:  *.test
Tests began at Mon Jun 20 01:34:08 PM PDT 2005
map.test

==== ii Test of int64 keys and int64 values FAILED
==== Contents of test case:

        exec ./test

---- Test setup failed:
In file included from ../../user/runtime.h:36,
                 from ii.c:1:
../../user/emul.h:29: error: redefinition of '__alloc_percpu'
/lib/modules/2.6.12-rc6-mm1/build/include/linux/percpu.h:44: error:
previous def
inition of '__alloc_percpu' was here
../../user/emul.h: In function `__alloc_percpu':
../../user/emul.h:31: error: dereferencing pointer to incomplete type
../../user/emul.h:37: error: dereferencing pointer to incomplete type
../../user/emul.h:39: error: dereferencing pointer to incomplete type
../../user/emul.h:42: error: dereferencing pointer to incomplete type
../../user/emul.h:42: error: dereferencing pointer to incomplete type
../../user/emul.h:42: error: dereferencing pointer to incomplete type
../../user/emul.h:42: error: dereferencing pointer to incomplete type
../../user/emul.h: At top level:
../../user/emul.h:51: error: redefinition of 'free_percpu'
/lib/modules/2.6.12-rc6-mm1/build/include/linux/percpu.h:51: error:
previous def
inition of 'free_percpu' was here
../../user/emul.h: In function `free_percpu':
../../user/emul.h:56: error: dereferencing pointer to incomplete type
==== ii FAILED


==== is Test of int64 keys and string values FAILED
==== Contents of test case:

-----Original Message-----
From: fche@redhat.com [mailto:fche@redhat.com] 
Sent: Monday, June 20, 2005 12:46 PM
To: Chen, Brad
Cc: systemtap@sources.redhat.com
Subject: Re: what if I wanted to write some tests...


Hi -

<brad.chen@intel.com> writes:

> Is there a way to check out the latest systemtap CVS tree, build it,
> and figure out where to start writing tests? [...]

Of course - you can check out the translator and/or runtime sources.
The former has various self-tests ("make check"); the latter has
various kprobes-flavoured test programs.


- FChE