Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 63723 invoked from network); 23 Oct 2000 07:44:02 -0000 Received: from analytik.analytikerna.se (192.58.197.10) by locus.apache.org with SMTP; 23 Oct 2000 07:44:02 -0000 Received: from lentus.se (IDENT:petern@up-dhcp2 [192.168.103.52]) by analytik.analytikerna.se (8.9.3/8.9.3) with ESMTP id JAA19132 for ; Mon, 23 Oct 2000 09:40:15 +0200 (MEST) Sender: petern@analytik.analytikerna.se Message-ID: <39F3EC77.D71FE9FA@lentus.se> Date: Mon, 23 Oct 2000 09:44:55 +0200 From: Peter Nordlund Organization: Lentus AB X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: ant-dev@jakarta.apache.org Subject: The Junit task, suggestion to add "haltontimeout" References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hi, I suggest that an attribute "haltontimeout" is added to the junit task and to the nested junit tasks, test and batchtest. The behaviour rigth now, if a test is not finished before the timeout, is that the test silently is cancelled and the build succeeds. (ant/2000-10-12) At least for me, tests that are not finished in time are regarded as failed tests. Any comments? /Regards, Peter