From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1102 invoked by alias); 16 Apr 2004 12:04:39 -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 1094 invoked from network); 16 Apr 2004 12:04:38 -0000 Received: from unknown (HELO cuddles.cambridge.redhat.com) (81.96.64.123) by sources.redhat.com with SMTP; 16 Apr 2004 12:04:38 -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 i3GC38P0023290; Fri, 16 Apr 2004 13:03:18 +0100 Received: (from aph@localhost) by redhat.com (8.12.8/8.12.8/Submit) id i3GC37Fu023286; Fri, 16 Apr 2004 13:03:07 +0100 From: Andrew Haley MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16511.52090.696553.529257@cuddles.cambridge.redhat.com> Date: Fri, 16 Apr 2004 12:04:00 -0000 To: Mark Wielaard Cc: Thomas Zander , mauve-discuss@sources.redhat.com Subject: Re: Some issues.. In-Reply-To: <1082114942.1971.9.camel@elsschot.wildebeest.org> References: <200404031504.41093.zander@javalobby.org> <16494.47358.415834.600012@cuddles.cambridge.redhat.com> <200404031540.39350.zander@javalobby.org> <16494.56084.958410.241061@cuddles.cambridge.redhat.com> <1082067738.1986.49.camel@elsschot.wildebeest.org> <16511.42905.101387.569375@cuddles.cambridge.redhat.com> <1082114942.1971.9.camel@elsschot.wildebeest.org> X-SW-Source: 2004-q2/txt/msg00042.txt.bz2 Mark Wielaard writes: > Hi, > > On Fri, 2004-04-16 at 11:30, Andrew Haley wrote: > > Mark Wielaard writes: > > > Which script is this? > > > > Err, the one in the BinaryCompatibility directory... > > > > It's called `foo', of course! :-) > > Aha. Wow. I never found that before. > 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. > I tried setting JAVA/JAVAC/GCJ as variables before invoking foo, but in > all cases it fails in weird and wonderful ways either compiling or > running. One issue seems to be that it does want the gnu/testlet/*.java > files, but this is never specified in its classpath or sourcepath. Well, I can't really understand the problem. BinaryCompatibilityTest.java is tagged JDK1.1, so it gets run along with the rest of Mauve. It then does all the grunt work and runs the test. So, if it fails, something else is wrong. > > > Is it documented? > > > > Yeah, right. > > :) > I admit to be guilty of not documenting my batch_run and runner script. > But a little blurb in the README wouldn't hurt. > If I promise to add something about my scripts, could you add something > about yours? At least how to invoke the thing... > > > > Might it be a good idea to add these tests to a separate module > > > like the visual tester and the verifier tests since they are > > > actually different from the rest of the mauve core library tests? > > > > Can you please be a little more specific about this? > > Since it seem to not be integrated with the rest of the tests (but I > might be wrong about this since I couldn't get them working at all) It is, it is! I want it to be run whenever we run Mauve. Andrew.