From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26276 invoked by alias); 31 Jul 2007 02:13:43 -0000 Received: (qmail 26265 invoked by uid 22791); 31 Jul 2007 02:13:42 -0000 X-Spam-Status: No, hits=1.3 required=5.0 tests=AWL,BAYES_20,DK_POLICY_SIGNSOME,TRACKER_ID,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org Received: from agminet01.oracle.com (HELO agminet01.oracle.com) (141.146.126.228) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 31 Jul 2007 02:13:40 +0000 Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l6V2DbJw003323 for ; Mon, 30 Jul 2007 21:13:37 -0500 Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id l6UN7AIM008657 for ; Mon, 30 Jul 2007 20:13:36 -0600 Received: from alchar.org by rcsmt252.oracle.com with ESMTP id 3081031441185847905; Mon, 30 Jul 2007 20:11:45 -0600 Date: Tue, 31 Jul 2007 02:13:00 -0000 From: Kris Van Hees To: frysk@sourceware.org Subject: TestLeakingFileDescriptor Message-ID: <20070731021143.GD22305@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00232.txt.bz2 I'd like to propose that the TestLeakingFileDescriptor test cases be marked as stress tests rather than regular tests, to avoid them being executed at every testsuite invocation. Reason for this proposal is two-fold: first of all, these tests are implicitly intermittent due to the fact that they depend on a behaviour that is not deterministic (the garbage collector does not actually do I/O resource mangement), and secondly, when they do fail they tend to cause a bunch of side effects (causing later tests to fail, causing daemon instances of TestRunner to never get torn down, ...). Cheers, Kris