From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25174 invoked by alias); 7 Sep 2007 18:37:11 -0000 Received: (qmail 25152 invoked by uid 48); 7 Sep 2007 18:37:02 -0000 Date: Fri, 07 Sep 2007 18:37:00 -0000 From: "kris dot van dot hees at oracle dot com" To: frysk-bugzilla@sourceware.org Message-ID: <20070907183702.5009.kris.van.hees@oracle.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/5009] New: tearDown problem: testFhpdVirtualStackTrace(frysk.hpd.TestStackCommands) X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00403.txt.bz2 List-Id: 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.