From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/17101] New: [rfe] timeout for stap
Date: Mon, 30 Jun 2014 13:51:00 -0000 [thread overview]
Message-ID: <bug-17101-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17101
Bug ID: 17101
Summary: [rfe] timeout for stap
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
I think it would be useful to implement some kind of run time limit. An option
like "--timeout N" and/or some environmental variable with similar meaning
would be handy.
Such an environmental variable might help when running testsuites. Exporting it
would be sufficient to adjust the stap behaviour during the testsuite run.
Also a check for inserted kernel modules + some cleanup might be performed in
the end, so that subsequent testcases can start running on top of a clean
table.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-06-30 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 13:51 mcermak at redhat dot com [this message]
2014-06-30 14:22 ` [Bug runtime/17101] " dsmith at redhat dot com
2014-06-30 16:34 ` fche at redhat dot com
2014-07-01 7:00 ` mcermak at redhat dot com
2014-07-03 18:45 ` fche at redhat dot com
2014-07-04 11:30 ` mcermak at redhat dot com
2014-07-04 14:26 ` fche at redhat dot com
2014-07-07 13:21 ` mcermak at redhat dot com
2014-07-07 15:39 ` dsmith at redhat dot com
2014-07-07 16:32 ` jistone at redhat dot com
2014-07-09 17:49 ` mcermak at redhat dot com
2014-07-15 19:50 ` ajakop 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=bug-17101-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).