From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11236 invoked by alias); 1 Oct 2009 15:52:08 -0000 Received: (qmail 11180 invoked by uid 48); 1 Oct 2009 15:51:53 -0000 Date: Thu, 01 Oct 2009 15:52:00 -0000 From: "fche at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20091001155152.10718.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug testsuite/10718] New: test separately distributed systemtap scripts X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00001.txt.bz2 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.