From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug testsuite/10718] New: test separately distributed systemtap scripts
Date: Thu, 01 Oct 2009 15:52:00 -0000 [thread overview]
Message-ID: <20091001155152.10718.fche@redhat.com> (raw)
Packages such as tuned-utils on fedora are starting to include
systemtap scripts in source form, being installed in /usr/*bin.
It would be convenient to test/link-to them as if they were
normal samples in our library, but without actually forking
them and bringing in a snapshot.
One possible solution is to extend the systemtap.examples/check.exp
logic to permit meta files to give URLs of external .stp files.
(For example,
http://git.fedorahosted.org/git/tuned.git/?p=tuned.git;a=blob_plain;f=contrib/diskdevstat;hb=HEAD).
We would include such meta files, including check|installcheck
directives and descriptions in our repo.
Running such external .stp programs is of course an act of faith
(that the given outside maintainer doesn't put harmful scripts
in there), so we should also add a "--enable-testsuite-external-meta"
or such autoconf option to enable installcheck'ing them.
--
Summary: test separately distributed systemtap scripts
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10718
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-10-01 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 15:52 fche at redhat dot com [this message]
2009-10-01 16:15 ` [Bug testsuite/10718] " pknirsch at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091001155152.10718.fche@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).