Hi Kurt, I think it is not possible to run full testsuite during build, because it expects that: - system has debuginfo for running kernel, - system has kprobes (and some other things) enabled in running kernel, - it is possible to load kernel modules.
I dont think all of this can be satisfied on buildds. It maybe be possible to run compile-only test, if there is debuginfo and headers package for running kernel that supports kprobes, but I don't see how it can be done using build-depends. I was thinking about making testsuite package. Then it can be used to test systemtap, once kernels with kprobes and debuginfo are available. But this should be done after build with sufficient privileges. 4 травня 2009 о 19:42 +0200 Kurt Roeckx написав(-ла): > Could you please run the testsuite during the build procces? > > It now seems to be using dh_auto_test, but that's not doing > anything. You're also atleast missing a build-dependency on > dejagnu. dh_auto_test is run by dh. It does nothing, because systemtap package uses dbs, so has different build directory. > > It should work by running "make check" in the src dir. > > I'm currently seeing alot of failed tests, and I have no idea > if that's normal or not: > === systemtap Summary === > > # of expected passes 104 > # of unexpected failures 171 > # of expected failures 202 > # of known failures 7 > # of untested testcases 289 > > (This might be related to having a standard Debian kernel. The > test should probably be skipped in that case.) This is probably normal, standard kernel does not have debuginfo and kprobes enabled. Regards, Eugeniy Meshcheryakov
signature.asc
Description: Digital signature