From: Mark Wielaard <mark@klomp.org>
To: Andrew Haley <aph@redhat.com>
Cc: Thomas Zander <zander@javalobby.org>, mauve-discuss@sources.redhat.com
Subject: Re: Some issues..
Date: Thu, 22 Apr 2004 21:41:00 -0000 [thread overview]
Message-ID: <1082669893.27234.160.camel@elsschot.wildebeest.org> (raw)
In-Reply-To: <16511.52090.696553.529257@cuddles.cambridge.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
Hi,
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
Do you get better/other results?
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-22 21:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 13:05 Thomas Zander
2004-04-03 13:16 ` Andrew Haley
2004-04-03 13:41 ` Thomas Zander
2004-04-03 15:42 ` Andrew Haley
2004-04-03 16:06 ` Thomas Zander
2004-04-15 22:22 ` Mark Wielaard
2004-04-16 9:31 ` Andrew Haley
2004-04-16 11:29 ` Mark Wielaard
2004-04-16 12:01 ` Some issues.. (batch_run and runner script documentation) Mark Wielaard
2004-04-16 12:04 ` Some issues Andrew Haley
2004-04-22 21:41 ` Mark Wielaard [this message]
2004-04-15 22:14 ` Mark Wielaard
2004-05-07 11:54 ` John Leuner
2004-05-07 13:25 ` Thomas
2004-04-23 9:12 Jeroen Frijters
2004-04-25 11:10 ` Mark Wielaard
2004-04-29 11:41 ` Andrew Haley
2004-04-29 13:16 ` Thomas
2004-04-29 15:29 ` Andrew Haley
2004-05-01 9:49 ` Thomas Zander
2004-05-02 12:27 ` Andrew Haley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1082669893.27234.160.camel@elsschot.wildebeest.org \
--to=mark@klomp.org \
--cc=aph@redhat.com \
--cc=mauve-discuss@sources.redhat.com \
--cc=zander@javalobby.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).