From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mauve-discuss-return-661-listarch-mauve-discuss=sources.redhat.com@sources.redhat.com>
Received: (qmail 17006 invoked by alias); 23 Apr 2004 09:12:00 -0000
Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:mauve-discuss-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/mauve-discuss/>
List-Post: <mailto:mauve-discuss@sources.redhat.com>
List-Help: <mailto:mauve-discuss-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: mauve-discuss-owner@sources.redhat.com
Received: (qmail 16993 invoked from network); 23 Apr 2004 09:11:58 -0000
Received: from unknown (HELO lembu.sumatrasoftware.com) (62.177.154.238)
  by sources.redhat.com with SMTP; 23 Apr 2004 09:11:58 -0000
Content-class: urn:content-classes:message
Subject: RE: Some issues..
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 23 Apr 2004 09:12:00 -0000
Message-ID: <788B535AB1F9CB49BB9C229372B50ACC0ADEA3@LEMBU.sumatrasoftware.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Jeroen Frijters" <jeroen@sumatra.nl>
To: "Mark Wielaard" <mark@klomp.org>,
	"Andrew Haley" <aph@redhat.com>
Cc: "Thomas Zander" <zander@javalobby.org>,
	<mauve-discuss@sources.redhat.com>
X-SW-Source: 2004-q2/txt/msg00048.txt.bz2

Mark Wielaard wrote:
> On Fri, 2004-04-16 at 14:03, Andrew Haley wrote:
> > Mark Wielaard writes:
> >  > Ehe, how do you use/invoke it?
> >=20
> > It gets invoked automatically when you run Mauve, at least on my
> > system.  BinaryCompatibilityTest.java is the driver that invokes it.
>=20
> Aha. And it uses Runtime.exec()... Which wasn't properly=20
> implemented in GNU Classpath proper. But we have it now (almost)!
>=20
> 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 <shiver>).

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.

On a somewhat related note, the invalid_port test in DatagramSocketTest2
assumes that it is illegal to create a DatagramSocket that listens on
port 21, but I don't believe that is part of the Java specification.

Regards,
Jeroen