From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9733 invoked by alias); 3 Jul 2007 17:59:05 -0000 Received: (qmail 9699 invoked by uid 48); 3 Jul 2007 17:58:54 -0000 Date: Tue, 03 Jul 2007 17:59:00 -0000 Message-ID: <20070703175854.9698.qmail@sourceware.org> From: "kris dot van dot hees at oracle dot com" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070703154532.4731.kris.van.hees@oracle.com> References: <20070703154532.4731.kris.van.hees@oracle.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4731] Junit going crazy after test failure 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/msg00016.txt.bz2 List-Id: ------- Additional Comments From kris dot van dot hees at oracle dot com 2007-07-03 17:58 ------- Well, if you look at the code, you see that the exception (Too many open files) is thrown from the Pipe object instantiation (in the native code) when tryGarbageCollect() is called repeatedly within a single attempt to create a pipe. So, clearly there was a problem with the garbage collection process not being able to ensure that there were fds available for creating the pipe. Regardless of the reason why this happened, junit shouldn't blow up over it. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4731 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.