From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22768 invoked by alias); 25 Apr 2004 11:10:46 -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 22760 invoked from network); 25 Apr 2004 11:10:43 -0000 Received: from unknown (HELO nescio.wildebeest.org) (82.161.94.186) by sources.redhat.com with SMTP; 25 Apr 2004 11:10:43 -0000 Received: from elsschot.wildebeest.org ([192.168.1.26] ident=mark) by nescio.wildebeest.org with esmtp (Exim 3.35 #1 (Debian)) id 1BHhWc-0003mE-00; Sun, 25 Apr 2004 13:10:18 +0200 Subject: RE: Some issues.. From: Mark Wielaard To: Jeroen Frijters Cc: Andrew Haley , Thomas Zander , mauve-discuss@sources.redhat.com In-Reply-To: <788B535AB1F9CB49BB9C229372B50ACC0ADEA3@LEMBU.sumatrasoftware.com> References: <788B535AB1F9CB49BB9C229372B50ACC0ADEA3@LEMBU.sumatrasoftware.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-F2GF/Y8IqIR6mLPEO939" Message-Id: <1082891420.27234.1377.camel@elsschot.wildebeest.org> Mime-Version: 1.0 Date: Sun, 25 Apr 2004 11:10:00 -0000 X-SW-Source: 2004-q2/txt/msg00049.txt.bz2 --=-F2GF/Y8IqIR6mLPEO939 Content-Type: multipart/mixed; boundary="=-ZN3F+/lqfnxRKTWegJTo" --=-ZN3F+/lqfnxRKTWegJTo Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Content-length: 1947 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? > > >=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 >=20 > I never really payed attention to this test, but now I see that it is > *nix specific (using shell script ). >=20 > 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. There is always Cygwin 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. > 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. I believe you are right. It is only an issue for processes without enough privileges on some systems (which normally reserve all post between 0 and 1024 for "system" services). So I committed this patch: 2004-04-25 Mark Wielaard * gnu/testlet/java/net/DatagramSocket/DatagramSocketTest2.java: Remo= ve RESERVED_PORT (21) test. Cheers, Mark --=-ZN3F+/lqfnxRKTWegJTo Content-Disposition: inline; filename=patch Content-Type: text/x-patch; name=patch; charset=iso-8859-1 Content-Transfer-Encoding: base64 Content-length: 1790 SW5kZXg6IGdudS90ZXN0bGV0L2phdmEvbmV0L0RhdGFncmFtU29ja2V0L0Rh dGFncmFtU29ja2V0VGVzdDIuamF2YQ0KPT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PQ0KUkNTIGZpbGU6IC9jdnMvbWF1dmUvbWF1dmUvZ251L3Rlc3RsZXQvamF2 YS9uZXQvRGF0YWdyYW1Tb2NrZXQvRGF0YWdyYW1Tb2NrZXRUZXN0Mi5qYXZh LHYNCnJldHJpZXZpbmcgcmV2aXNpb24gMS41DQpkaWZmIC11IC1yMS41IERh dGFncmFtU29ja2V0VGVzdDIuamF2YQ0KLS0tIGdudS90ZXN0bGV0L2phdmEv bmV0L0RhdGFncmFtU29ja2V0L0RhdGFncmFtU29ja2V0VGVzdDIuamF2YQky OSBPY3QgMjAwMyAxNDozOToyMCAtMDAwMAkxLjUNCisrKyBnbnUvdGVzdGxl dC9qYXZhL25ldC9EYXRhZ3JhbVNvY2tldC9EYXRhZ3JhbVNvY2tldFRlc3Qy LmphdmEJMjUgQXByIDIwMDQgMTE6MDg6NTEgLTAwMDANCkBAIC01OSw3ICs1 OSw2IEBADQogew0KIAlmaW5hbCBzdGF0aWMgaW50IElOVkFMSURfUE9SVCA9 IC0xOw0KIAlmaW5hbCBzdGF0aWMgaW50IEVDSE9fUE9SVCA9IDc7DQotCWZp bmFsIHN0YXRpYyBpbnQgUkVTRVJWRURfUE9SVCA9IDIxOw0KIAlmaW5hbCBz dGF0aWMgaW50IEdPT0RfUE9SVCA9IDM3Nzc3Ow0KIAlmaW5hbCBzdGF0aWMg aW50IE1BWF9QT1JUID0gNjU1MzU7DQogDQpAQCAtOTMsMjUgKzkyLDYgQEAN CiAJcHVibGljIHZvaWQgaW52YWxpZF9wb3J0KCkNCiAJew0KIAkJaGFybmVz cy5jaGVja1BvaW50KCJpbnZhbGlkX3BvcnQiKTsNCi0JCXRyeQ0KLQkJew0K LQkJCURhdGFncmFtU29ja2V0IHNvY2sgPSBuZXcgRGF0YWdyYW1Tb2NrZXQo UkVTRVJWRURfUE9SVCk7DQotCQkJZXJyb3Jtc2coImludmFsaWRfcG9ydCIs IDEsIHRydWUsICJCaW5kRXhjZXB0aW9uIik7DQotCQl9DQotCQljYXRjaCAo QmluZEV4Y2VwdGlvbiBlKQ0KLQkJew0KLQkJCWhhcm5lc3MuY2hlY2sodHJ1 ZSk7DQotCQl9DQotCQljYXRjaCAoU29ja2V0RXhjZXB0aW9uIGUpDQotCQl7 DQotCQkJZXJyb3Jtc2coImludmFsaWRfcG9ydCIsIDEsIGZhbHNlLCAiU29j a2V0RXhjZXB0aW9uIik7DQotCQl9DQotCQljYXRjaCAoTnVsbFBvaW50ZXJF eGNlcHRpb24gZSkNCi0JCXsNCi0JCQllcnJvcm1zZygiaW52YWxpZF9wb3J0 IiwgMSwgZmFsc2UsICJOdWxsUG9pbnRlckV4Y2VwdGlvbiIpOw0KLQkJCWUu cHJpbnRTdGFja1RyYWNlKCk7DQotCQl9DQotDQogCQl0cnkNCiAJCXsNCiAJ CQlEYXRhZ3JhbVNvY2tldCBzb2NrID0gbmV3IERhdGFncmFtU29ja2V0KElO VkFMSURfUE9SVCk7DQo= --=-ZN3F+/lqfnxRKTWegJTo-- --=-F2GF/Y8IqIR6mLPEO939 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAi5ycxVhZCJWr9QwRAreFAJ4+PLAbcPp+Pub24NN8/Vp3etKtfwCfdO2J hp3ljYPOirdVQo+xxVJzVjc= =FHyz -----END PGP SIGNATURE----- --=-F2GF/Y8IqIR6mLPEO939--