From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10541 invoked by alias); 17 Mar 2006 22:34:21 -0000 Received: (qmail 10532 invoked by uid 22791); 17 Mar 2006 22:34:20 -0000 X-Spam-Check-By: sourceware.org Received: from mail21.bluewin.ch (HELO mail21.bluewin.ch) (195.186.18.66) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Mar 2006 22:34:17 +0000 Received: from [192.168.1.64] (83.76.222.211) by mail21.bluewin.ch (Bluewin 7.2.071) id 43E4A5E800D5808A for mauve-discuss@sourceware.org; Fri, 17 Mar 2006 22:34:14 +0000 Message-ID: <441B3990.6060306@bluewin.ch> Date: Fri, 17 Mar 2006 22:34:00 -0000 From: Audrius Meskauskas User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) MIME-Version: 1.0 To: Mauve discuss Subject: Re: Mauve wishlist References: <1142613140.3805.20.camel@rh-ibm-t41> In-Reply-To: <1142613140.3805.20.camel@rh-ibm-t41> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact mauve-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00064.txt.bz2 1. My largest problem was hangings during the tests. When an error report is just an error report, hanging blocks all testing process, requiring to remove such test manually. The problem is difficult to solve, but maybe the tests could run in the separate thread, and the threads of the normally terminated tests could be reused. JUnit, by the way, also has the same problem. 2. Probably the error reports could include the line, where the harness check failed. The stack trace of the newly constructed exception could be used to get the line information. The uncaught exception reports could also provide more information, not just "uncaught exception", as it is now. Regards Audrius Meskauskas.