From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16855 invoked by alias); 3 Jul 2007 19:46:09 -0000 Received: (qmail 16825 invoked by uid 48); 3 Jul 2007 19:45:58 -0000 Date: Tue, 03 Jul 2007 19:46:00 -0000 Message-ID: <20070703194558.16824.qmail@sourceware.org> From: "cagney at redhat 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/msg00031.txt.bz2 List-Id: ------- Additional Comments From cagney at redhat dot com 2007-07-03 19:45 ------- (In reply to comment #2) > 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. Right. Is there any external factor that could be triggering this difference in behavour? > Regardless of the reason why this happened, junit shouldn't blow up over it. While one is disputing that JUnit and the JVM should handle this more gracefully, running out of FDs is an extreem situtation and not well-defined so we may need to cut some slack here. -- 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.