From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <frysk-bugzilla-return-2574-listarch-frysk-bugzilla=sourceware.org@sourceware.org>
Received: (qmail 16400 invoked by alias); 13 Sep 2007 15:46:59 -0000
Received: (qmail 16306 invoked by uid 48); 13 Sep 2007 15:46:47 -0000
Date: Thu, 13 Sep 2007 15:46:00 -0000
From: "kris dot van dot hees at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Message-ID: <20070913154647.5029.kris.van.hees@oracle.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug general/5029] New: tearDown problem: testCloneThenKillAttached(frysk.proc.TestProcTasksObserver)
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:frysk-bugzilla-subscribe@sourceware.org>
List-Post: <mailto:frysk-bugzilla@sourceware.org>
List-Help: <mailto:frysk-bugzilla-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: frysk-bugzilla-owner@sourceware.org
X-SW-Source: 2007-q3/txt/msg00409.txt.bz2
List-Id: <frysk-bugzilla.sourceware.org>

x86, FC6:

Running testCloneThenKillAttached(frysk.proc.TestProcTasksObserver) ...FAIL
  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.

-- 
           Summary: tearDown problem:
                    testCloneThenKillAttached(frysk.proc.TestProcTasksObserv
                    er)
           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=5029

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.