public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "kris dot van dot hees at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5009] New: tearDown problem: testFhpdVirtualStackTrace(frysk.hpd.TestStackCommands)
Date: Fri, 07 Sep 2007 18:37:00 -0000 [thread overview]
Message-ID: <20070907183702.5009.kris.van.hees@oracle.com> (raw)
On x86, FC6:
testFhpdVirtualStackTrace(frysk.hpd.TestStackCommands)junit.framework.AssertionFailedError:
tearDown timed out waiting for children; this is caused by either: a wedged
process (kernel, unlikely); or a process not registered for tear-down. Either
way this is bad as the stray process will likely confuse the next test. The fix
is to find and register the unknown process. Workaround by running tests
individually.
at frysk.testbed.TearDownProcess.tearDown(TestRunner)
at frysk.testbed.TestLib.tearDown(TestRunner)
at frysk.hpd.TestLib.tearDown(TestRunner)
at frysk.junit.Runner.runCases(TestRunner)
at frysk.junit.Runner.runArchCases(TestRunner)
at frysk.junit.Runner.runTestCases(TestRunner)
at TestRunner.main(TestRunner)
--
Summary: tearDown problem:
testFhpdVirtualStackTrace(frysk.hpd.TestStackCommands)
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: kris dot van dot hees at oracle dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=5009
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-09-07 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 18:37 kris dot van dot hees at oracle dot com [this message]
2007-09-07 18:40 ` [Bug general/5009] " kris dot van dot hees at oracle dot com
2007-09-13 15:47 ` swagiaal at redhat dot com
2007-09-13 15:48 ` swagiaal 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=20070907183702.5009.kris.van.hees@oracle.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=frysk-bugzilla@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).