Debian Bug report logs -
#526957
systemtap: Run test suite.
Reported by: Kurt Roeckx <kurt@roeckx.be>
Date: Mon, 4 May 2009 17:45:02 UTC
Severity: wishlist
Found in version systemtap/0.0.20090502-1
Fixed in version systemtap/4.1-2
Done: Emanuele Rocca <ema@debian.org>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, Євгеній Мещеряков <eugen@debian.org>:
Bug#526957; Package systemtap.
(Mon, 04 May 2009 17:45:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Kurt Roeckx <kurt@roeckx.be>:
New Bug report received and forwarded. Copy sent to Євгеній Мещеряков <eugen@debian.org>.
(Mon, 04 May 2009 17:45:04 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: systemtap
Version: 0.0.20090502-1
Severity: wishlist
Hi,
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.
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.)
Kurt
Information forwarded
to debian-bugs-dist@lists.debian.org, Євгеній Мещеряков <eugen@debian.org>:
Bug#526957; Package systemtap.
(Mon, 04 May 2009 18:27:02 GMT) (full text, mbox, link).
Acknowledgement sent
to "Frank Ch. Eigler" <fche@redhat.com>:
Extra info received and forwarded to list. Copy sent to Євгеній Мещеряков <eugen@debian.org>.
(Mon, 04 May 2009 18:27:02 GMT) (full text, mbox, link).
Message #10 received at 526957@bugs.debian.org (full text, mbox, reply):
Hi -
On Mon, May 04, 2009 at 07:42:33PM +0200, Kurt Roeckx wrote:
> Could you please run the testsuite during the build procces?
> [...]
> It should work by running "make check" in the src dir.
Of even "make installcheck" for actual execution of systemtap test
scripts (as opposed to their mere compilation).
> 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
That's only "normal" for a mismatching- or absent-debuginfo
installation.
- FChE
Information forwarded
to debian-bugs-dist@lists.debian.org, Євгеній Мещеряков <eugen@debian.org>:
Bug#526957; Package systemtap.
(Mon, 04 May 2009 19:54:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Kurt Roeckx <kurt@roeckx.be>:
Extra info received and forwarded to list. Copy sent to Євгеній Мещеряков <eugen@debian.org>.
(Mon, 04 May 2009 19:54:04 GMT) (full text, mbox, link).
Message #15 received at 526957@bugs.debian.org (full text, mbox, reply):
On Mon, May 04, 2009 at 02:25:27PM -0400, Frank Ch. Eigler wrote:
> Hi -
>
> On Mon, May 04, 2009 at 07:42:33PM +0200, Kurt Roeckx wrote:
>
> > Could you please run the testsuite during the build procces?
> > [...]
> > It should work by running "make check" in the src dir.
>
> Of even "make installcheck" for actual execution of systemtap test
> scripts (as opposed to their mere compilation).
installcheck seems to expect things to be installed on the system?
Is there some way to override that so that it can be run from a
temporary dir?
I also doubt that it's something that is going to work on any of
the buildd machines. I assume it's going to require root, and the
machines will probably not run a kernel that is going to support it.
Kurt
Information forwarded
to debian-bugs-dist@lists.debian.org, Євгеній Мещеряков <eugen@debian.org>:
Bug#526957; Package systemtap.
(Mon, 04 May 2009 20:18:07 GMT) (full text, mbox, link).
Acknowledgement sent
to "Frank Ch. Eigler" <fche@redhat.com>:
Extra info received and forwarded to list. Copy sent to Євгеній Мещеряков <eugen@debian.org>.
(Mon, 04 May 2009 20:18:07 GMT) (full text, mbox, link).
Message #20 received at 526957@bugs.debian.org (full text, mbox, reply):
Hi -
On Mon, May 04, 2009 at 09:52:58PM +0200, Kurt Roeckx wrote:
> > Or even "make installcheck" for actual execution of systemtap test
> > scripts (as opposed to their mere compilation).
>
> installcheck seems to expect things to be installed on the system?
> Is there some way to override that so that it can be run from a
> temporary dir?
(Well, one can configure/make/make-install into a temporary directory.)
> I also doubt that it's something that is going to work on any of the
> build machines. I assume it's going to require root, and the
> machines will probably not run a kernel that is going to support it.
Right, it is an aggressive test suite which does require root access.
OTOH the build machines still need nearly the same support in the
sense of installed debugging data, if plain "make check" is to test
enough stuff.
- FChE
Information forwarded
to debian-bugs-dist@lists.debian.org, Євгеній Мещеряков <eugen@debian.org>:
Bug#526957; Package systemtap.
(Tue, 05 May 2009 10:00:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Eugeniy Meshcheryakov <eugen@debian.org>:
Extra info received and forwarded to list. Copy sent to Євгеній Мещеряков <eugen@debian.org>.
(Tue, 05 May 2009 10:00:03 GMT) (full text, mbox, link).
Message #25 received at 526957@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
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 (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Ritesh Raj Sarraf <rrs@debian.org>:
Bug#526957; Package systemtap.
(Thu, 11 Aug 2011 14:03:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Timo Juhani Lindfors <timo.lindfors@iki.fi>:
Extra info received and forwarded to list. Copy sent to Ritesh Raj Sarraf <rrs@debian.org>.
(Thu, 11 Aug 2011 14:03:04 GMT) (full text, mbox, link).
Message #30 received at 526957@bugs.debian.org (full text, mbox, reply):
Hi,
[ This is resend #1 since even after four hours the email does not seem
to have reached bugs.debian.org. ]
inspired by the TDDD BoF at Debconf I experimented a bit with DEP-8
(autopkgtest). Using the bug526957_autopkgtest branch in
http://iki.fi/lindi/git/systemtap.git/
I can now run the upstream testsuite against my installation with
$ sudo apt-get install autopkgtest
$ apt-get --download-only source systemtap
$ sudo adt-run --no-built-binaries systemtap_1.6-1lindi3.dsc --- adt-virt-null
And yes, it does indeed test the _installed_ package. It just needs the
source package since the tests are stored there. Autopkgtest supports
running the tests in a separate xen instance so that you don't need to
worry about systemtap crashing the kernel. I did not test this part yet,
however. In the process I filed a few bugs against autopkgtest, you need
patches from those to actually do the above :-)
The full output is at
http://lindi.iki.fi/lindi/systemtap/systemtap_1.6-1_amd64_autopkgtest_20110811.txt.bz2
but the last lines of it are:
...
PASS: unprivilegedko: module("*scsi*").function("*") {}
PASS: unprivilegedko: kernel.mark("*") {}
PASS: unprivilegedko: kernel.mark("*").format("*") {}
Running /tmp/tmp.Lak8Xkffb1/dsc0-build/systemtap-1.6/testsuite/systemtap.unprivileged/unprivilegedok.exp ...
PASS: unprivilegedok compile
PASS: unprivilegedok: %(CONFIG_UTRACE=="y" %? process("foo").begin %: end %)
PASS: unprivilegedok: %(CONFIG_UTRACE=="y" %? process("foo").function("bar") %: end %)
PASS: unprivilegedok: %(CONFIG_UTRACE=="y" %? process("foo").function("bar").call %: end %)
PASS: unprivilegedok: %(CONFIG_UTRACE=="y" %? process("foo").function("bar").return %: end %)
=== systemtap Summary ===
# of expected passes 1077
# of unexpected failures 87
# of unexpected successes 8
# of expected failures 232
# of known failures 2
# of untested testcases 269
# of unsupported tests 2
adt-run: trace: & dsc0t-upstream-testsuite: ----------------------------------------]
adt-run: trace: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ tests done.
adt-run: trace: ** stop
adt-run: trace: ** close, scratch=tb-scratch~/tmp/tmp.Lak8Xkffb1:-/|/tmp/tmp.Lak8Xkffb1/!
-Timo
Message sent on
to Kurt Roeckx <kurt@roeckx.be>:
Bug#526957.
(Thu, 11 Aug 2011 14:03:05 GMT) (full text, mbox, link).
Reply sent
to Emanuele Rocca <ema@debian.org>:
You have taken responsibility.
(Fri, 19 Jul 2019 21:15:06 GMT) (full text, mbox, link).
Notification sent
to Kurt Roeckx <kurt@roeckx.be>:
Bug acknowledged by developer.
(Fri, 19 Jul 2019 21:15:06 GMT) (full text, mbox, link).
Message #38 received at 526957-close@bugs.debian.org (full text, mbox, reply):
Source: systemtap
Source-Version: 4.1-2
We believe that the bug you reported is fixed in the latest version of
systemtap, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 526957@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emanuele Rocca <ema@debian.org> (supplier of updated systemtap package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 17 Jul 2019 22:29:10 +0200
Source: systemtap
Binary: systemtap systemtap-client systemtap-common systemtap-dbgsym systemtap-doc systemtap-runtime systemtap-runtime-dbgsym systemtap-sdt-dev systemtap-server systemtap-server-dbgsym
Architecture: source amd64 all
Version: 4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf <rrs@debian.org>
Changed-By: Emanuele Rocca <ema@debian.org>
Description:
systemtap - instrumentation system for Linux
systemtap-client - instrumentation system for Linux (client for compile server)
systemtap-common - instrumentation system for Linux (common component)
systemtap-doc - documentation and examples for SystemTap
systemtap-runtime - instrumentation system for Linux (runtime component)
systemtap-sdt-dev - statically defined probes development files
systemtap-server - instrumentation system for Linux (compile server)
Closes: 526957 932440
Changes:
systemtap (4.1-2) unstable; urgency=medium
.
* Patch stap-prep to check for the right kernel debug symbols package (-dbg
rather than -dbgsym)
* Run basic stap-prep testing and upstream test suite via autopkgtest
(Closes: #526957)
* Use the Salsa CI Pipeline (see debian/salsa-ci.yml)
* Ship debian/systemtap-common.emacsen-compat (Closes: #932440)
Checksums-Sha1:
fb9de3486dfccf30214cd3b331a203722473f68d 2781 systemtap_4.1-2.dsc
b9cc8247da85ffac23dceb8461756c25f34be94e 88308 systemtap_4.1-2.debian.tar.xz
a9c4e3f00dae872ec4fb9b62f4d1eb05dcd7145e 19476 systemtap-client_4.1-2_amd64.deb
e65e1b6a673f4594c1a5bed85092816fed51da5e 604256 systemtap-common_4.1-2_all.deb
ac95425a0294064fa663193a11c67e278d588ea1 22495764 systemtap-dbgsym_4.1-2_amd64.deb
50ee9a4419dfa9834ec529c42a24974f9a1ddeb9 2201684 systemtap-doc_4.1-2_all.deb
50944d0cd1ce6d5a9df302b707be135421212dfe 1290340 systemtap-runtime-dbgsym_4.1-2_amd64.deb
e2dd859ef3388e3fd0039e3989cee27b037f8dfa 140696 systemtap-runtime_4.1-2_amd64.deb
995aebe41fd58ab8bb41bacef3d4386738c46f83 28692 systemtap-sdt-dev_4.1-2_amd64.deb
a471744cd09ee0ea701ca898d0a7adf8bb639d1a 2181712 systemtap-server-dbgsym_4.1-2_amd64.deb
9db6b6361772a4725b9f2d6a5c8d686f02db190d 152452 systemtap-server_4.1-2_amd64.deb
9b9393fdab16885f14d38443171362950fcb292d 12378 systemtap_4.1-2_amd64.buildinfo
6ab55da27d1d3582fa77a85782009b692a0da795 1223900 systemtap_4.1-2_amd64.deb
Checksums-Sha256:
836230adfe192edd1d2d75aba1ad47542e6d956ee5bef6dc4dcc55684fa4bff0 2781 systemtap_4.1-2.dsc
c885a13df1c281cd522c446f2b8e6db3d48d1a95f7b93890a2ec9b1fd01b053d 88308 systemtap_4.1-2.debian.tar.xz
7770dc6751c7c042dec3a82beca726c2fb796f4facdec400d68a26568ff8c391 19476 systemtap-client_4.1-2_amd64.deb
7b9d9402e0c9278920f0be904dbbf7c2c991ff4f4fba81c83ccdf92e98a3c2c8 604256 systemtap-common_4.1-2_all.deb
511f2b6dde86913248ca4ebbab9118538ba203590982900692af0dadb6420a92 22495764 systemtap-dbgsym_4.1-2_amd64.deb
dc0632420948fbb849c6ccb5b6174d2469e28aee8354e9fcb702f03812dc0fc4 2201684 systemtap-doc_4.1-2_all.deb
cf37fbdc2becf9b122c3b8f725b6ad74b27efeeb5bfade6ab8f1d959f8417da5 1290340 systemtap-runtime-dbgsym_4.1-2_amd64.deb
04c83e7724f810a06ed47f206a6990c99f896165b91b303fbfc219c9417039f0 140696 systemtap-runtime_4.1-2_amd64.deb
ccb78c63c73e853f0474d035739f11c66eedaf8b65703600610714865bb96491 28692 systemtap-sdt-dev_4.1-2_amd64.deb
1d3b50c6285e5062d16d34b699de87b679acfb23448c4b6252a941b80776e036 2181712 systemtap-server-dbgsym_4.1-2_amd64.deb
835c41b62ada657d5e91febcc918c4ae570ebcb9dd208fa0c706b2a030a5ff7a 152452 systemtap-server_4.1-2_amd64.deb
8dd22c7faf88478e0677b1e600b5db6095fa8b818affd14f2f7117ea9bf6c08c 12378 systemtap_4.1-2_amd64.buildinfo
84408048b399e61e4d2bd71ecd2d8d9058194ac798845ad5c1e6de85546b606d 1223900 systemtap_4.1-2_amd64.deb
Files:
000c1445d98307055107735ee7bf97ca 2781 devel optional systemtap_4.1-2.dsc
cb79d07e0f217a769d065eb8f8ef8878 88308 devel optional systemtap_4.1-2.debian.tar.xz
1e65580a71c900ce52e91979616d21a3 19476 devel optional systemtap-client_4.1-2_amd64.deb
9134f5bac7490d348263c6de6e7a9131 604256 devel optional systemtap-common_4.1-2_all.deb
0803a8aa418d90245a202bb697da5af6 22495764 debug optional systemtap-dbgsym_4.1-2_amd64.deb
6abe64b65f8be2e2b8850f45b1340280 2201684 doc optional systemtap-doc_4.1-2_all.deb
100630299fd5efe2455ac4d520ee644e 1290340 debug optional systemtap-runtime-dbgsym_4.1-2_amd64.deb
d8b42d92d3a240812eda2dfb8d9c136d 140696 devel optional systemtap-runtime_4.1-2_amd64.deb
9eadb3db78351833f09294f3eeb20abc 28692 devel optional systemtap-sdt-dev_4.1-2_amd64.deb
0067106676a96d245747a08c43e8ff37 2181712 debug optional systemtap-server-dbgsym_4.1-2_amd64.deb
97f60f0e75bd7413831e70ce7bb90e93 152452 devel optional systemtap-server_4.1-2_amd64.deb
433fcfcfa1b4f7f6c8ac908aae5843f5 12378 devel optional systemtap_4.1-2_amd64.buildinfo
d5a7740dd074c58fdf3c56ccd49e610d 1223900 devel optional systemtap_4.1-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCgAtFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAl0yLwwPHGVtYUBkZWJp
YW4ub3JnAAoJENUIWgdQ/bejbYoP/0FLfDYyvUueA8gk5MUOUwZ2aVqbFV1FXIsm
ECTk3z25LtJzj/Jj4mOkMVHq694BwIFdCYgjtdPUdzxoX15xogIEMona7fcuZQF7
OvKExbakEnlc7PdaUrqsd2PEdGQ+S2PpURY2QarOZEg3l2MhMbQMDg7UvN/33cet
WagY4WL5+9vorU4hgMtB3J2Neq/g46Iabxm3rR3V8iCGHyiqYSwl18YFYJZYQL5I
zdbBbpbtTcDk6Jpr0kDK5tHySuO+pDB/Ja/95AAYigfE/C6VHTTWfj08EcD0G2VI
PDpunNSnTUDJihdXk1wgINfV3FcKKf3XuOoWZcWcZllefOWotmTecXFKvLnymMQ/
MXhpMHdL5/5R+UJ+iAOLlbpkYwocu1VHl3iZxHJyKVM+8CV9Hle5tFN7N+sCWjLa
McsEXfbrK9iQelaZghehwKNC/V7wAgHBvQE9DYZODugC6+1mK4t0S2VI8E8zvQIh
ZsixsRlNJZGcBr3uVRKKXCVUzkfkivWdrTAGAv/siRAiPagg59MpMS9Thp3CNAPj
ryMtb4637y1RrY4RlXHNf+8WpS91Sq/GKTHVd/j8ezbowxMu/JVYUtkr5M4lT9o/
ZW82sW7D9aSuaaH7J1BryvSZueROGhczNo4uyd6Mb+Ni67pp1T48LXPsR0JOgXg8
sGRz7MTY
=22ed
-----END PGP SIGNATURE-----
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Sun, 18 Aug 2019 07:28:01 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Thu Aug 8 01:42:22 2024;
Machine Name:
buxtehude
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.