From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1686 invoked by alias); 29 Apr 2004 11:41:43 -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 1646 invoked from network); 29 Apr 2004 11:41:41 -0000 Received: from unknown (HELO cuddles.cambridge.redhat.com) (81.96.64.123) by sources.redhat.com with SMTP; 29 Apr 2004 11:41:41 -0000 Received: from redhat.com (localhost.localdomain [127.0.0.1]) by cuddles.cambridge.redhat.com (8.12.8/8.12.8) with ESMTP id i3TBdeV3012993; Thu, 29 Apr 2004 12:39:50 +0100 Received: (from aph@localhost) by redhat.com (8.12.8/8.12.8/Submit) id i3TBddaC012989; Thu, 29 Apr 2004 12:39:39 +0100 From: Andrew Haley MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16528.59771.25101.572974@cuddles.cambridge.redhat.com> Date: Thu, 29 Apr 2004 11:41:00 -0000 To: Mark Wielaard Cc: Jeroen Frijters , Thomas Zander , mauve-discuss@sources.redhat.com Subject: RE: Some issues.. In-Reply-To: <1082891420.27234.1377.camel@elsschot.wildebeest.org> References: <788B535AB1F9CB49BB9C229372B50ACC0ADEA3@LEMBU.sumatrasoftware.com> <1082891420.27234.1377.camel@elsschot.wildebeest.org> X-SW-Source: 2004-q2/txt/msg00056.txt.bz2 Mark Wielaard writes: > Hi, > > On Fri, 2004-04-23 at 11:11, Jeroen Frijters wrote: > > Mark Wielaard wrote: > > > On Fri, 2004-04-16 at 14:03, Andrew Haley wrote: > > > > Mark Wielaard writes: > > > > > Ehe, how do you use/invoke it? > > > > > > > > It gets invoked automatically when you run Mauve, at least on my > > > > system. BinaryCompatibilityTest.java is the driver that invokes it. > > > > > > Aha. And it uses Runtime.exec()... Which wasn't properly > > > implemented in GNU Classpath proper. But we have it now (almost)! > > > > > > ow that I can run it I see that kaffe, jamvm and gij all fail most of > > > the tests. Each of IL bin_01 till IL bin_18 fails 5 or 6 times giving: > > > 107 of 125 tests failed > > > > I never really payed attention to this test, but now I see that it is > > *nix specific (using shell script ). > > > > What is the policy for Mauve? I realise most of you don't care > > about/for Windows, but personally I do. > > So I support Mark's earlier suggestion/request to move this to a > > separate section. Well, alright, as long as you don't have to run it separately if you are on a *nix system. > There is always Cygwin I think Windows has its own *nix compatible subsystem now. But I'm not an expert... > But I do think it might be better to separate out this test from the > rest of Mauve proper. On the other hand, if you have a non-GNUish/Posix > system then you can always disable this one test. Separating it out > without a mechanism for running the tests on multiple systems isn't > really worth it I guess. I don't see the problem, really. If it doesn't run on some system, what is lost? All that happens is a few test failures. There's no reason why someone who is using an unfree OS can't rewrite this test in pure Java if they really need it. But I note that this shell script will work even on MacOS these days. Andrew.