From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2685 invoked by alias); 7 Apr 2004 06:01:08 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 2654 invoked from network); 7 Apr 2004 06:01:01 -0000 Received: from unknown (HELO piglet.dstc.edu.au) (130.102.176.1) by sources.redhat.com with SMTP; 7 Apr 2004 06:01:01 -0000 Received: from dstc.edu.au (credence.dstc.edu.au [130.102.177.137]) by piglet.dstc.edu.au (8.12.10/8.12.10) with ESMTP id i3760YmT005287; Wed, 7 Apr 2004 16:00:34 +1000 (EST) Message-Id: <200404070600.i3760YmT005287@piglet.dstc.edu.au> To: tromey@redhat.com cc: Archie Cobbs , Sascha Brawer , mauve-discuss@sources.redhat.com, commit-classpath@gnu.org, crawley@dstc.edu.au Subject: Re: Mauve patch In-Reply-To: Message from Tom Tromey of "06 Apr 2004 23:31:38 CST." <87vfkc4amd.fsf@fleche.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Apr 2004 06:01:00 -0000 From: Stephen Crawley X-Scanned-By: MIMEDefang 2.39 (DSTC) X-SW-Source: 2004-q2/txt/msg00011.txt.bz2 Hi Tom, > Perhaps it is better to just remove the test. That would be my preferred option. > Or make a new "unportable" section of Mauve, since some things > seemingly can't be tested. I think it would be better for each JVM projects to manage its own non-portable testcases. In Kissme for example, there is a small regression testsuite (called "HitMe") that tests some of Kissme's low level and VM specific features. The HitMe harness assumes that less of the VM infrastructure is working that the Mauve harness does. There is even a version that avoids using java.lang.io.* and uses the rc returned using System.exit() to signal test success / failure. Some HitMe tests require special Kissme commandline arguments. The makefile understands this ... -- Steve