From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/13332] skipped.exp testcase can freeze processes/system
Date: Mon, 07 Nov 2011 10:54:00 -0000 [thread overview]
Message-ID: <bug-13332-6586-NCiEV7afW5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13332-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13332
--- Comment #1 from Mark Wielaard <mjw at redhat dot com> 2011-11-07 10:53:15 UTC ---
Since this test keep messing up systems I have made it UNTESTED for now:
commit 3780aaa7c3ddd4af58adcb24c186af0738340935
Author: Mark Wielaard <mjw@redhat.com>
Date: Mon Nov 7 11:52:17 2011 +0100
PR13332 skipped.exp testcase can freeze processes/system.
Mark skipped.exp as untested for now.
diff --git a/testsuite/systemtap.base/skipped.exp
b/testsuite/systemtap.base/skipped.exp
index 0239efc..bfb74ee 100644
--- a/testsuite/systemtap.base/skipped.exp
+++ b/testsuite/systemtap.base/skipped.exp
@@ -5,6 +5,10 @@ if {! [installtest_p]} { untested $test; return }
set nr_cpus [exec sh -c "grep ^processor /proc/cpuinfo | wc -l"]
if {$nr_cpus < 2} { unsupported $test; return }
+# See PR13332 skipped.exp testcase can freeze processes/system
+untested "$test PR13332 skipped.exp testcase can freeze processes/system"
+return
+
set script {
global f
probe timer.profile { f++; snooze() }
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
prev parent reply other threads:[~2011-11-07 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 19:53 [Bug testsuite/13332] New: " mjw at redhat dot com
2011-11-07 10:54 ` mjw at redhat dot com [this message]
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-13332-6586-NCiEV7afW5@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).