public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Stephen Crawley <crawley@dstc.edu.au>
Cc: "James Damour (Suvarov454)" <suvarov454@users.sourceforge.net>,
	 mauve-discuss@sources.redhat.com, crawley@piglet.dstc.edu.au
Subject: Re: Mauve halts after first error.
Date: Mon, 05 Jul 2004 06:18:00 -0000	[thread overview]
Message-ID: <1089008192.24717.289.camel@localhost> (raw)
In-Reply-To: <200407050342.i653gkij003660@piglet.dstc.edu.au>

[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]

Hi,

On Mon, 2004-07-05 at 05:42, Stephen Crawley wrote:
> I ran into this particular problem too.  Someone has checked in a Mauve
> test case that refers to a class that Classpath does not yet support.
> [I wish people wouldn't do this!]
> 
> The workaround is to add the following line to your keys file:
> 
> !java.beans.Expression.check

Note that in this particular case GNU Classpath now includes this class
(since yesterday, just in time for 0.10-pre1!).

Since I also ran into this problem so often (or having a runtime crash
or hang on a particular test) I created the batch_run and runner scripts
which are now included in mauve CVS, but you need to edit them by hand
at the moment for your compiler/runtime setup. See the README:

        An alternative way to compiling and running all tests is the
        batch_run script.  This makes it easy to run all test in one
        batch without worrying wheter all tests compile and/or running
        them crashes or hangs the runtime.
        
        batch_run and the runner helper script aren't integrated with
        the configure setup yet so you will have to edit them by hand to
        explicitly set the COMPILER variable in batch_run and the
        RUNTIME variable in runner. Optionally you can also change the
        KEYS setting in batch_run if you don't want to run all tests. 
        You can also set the variable NATIVE=true in batch_run when you
        want to use gcj (without -C) in native mode.
        
        When a test cannot be compiled with the given COMPILER batch_run
        will output FAIL: <testname> COMPILE FAILED and go on with the
        next test. If the runner detects a runtime crash or timeout
        (runner variable WAIT=60 seconds) it will output FAIL:
        <testname> CRASH or TIMEOUT.

Cheers,

Mark

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-07-05  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jdamour@nycap.rr.com>
2004-07-04 23:57 ` James Damour
2004-07-05  3:43   ` Stephen Crawley
2004-07-05  6:18     ` Mark Wielaard [this message]

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=1089008192.24717.289.camel@localhost \
    --to=mark@klomp.org \
    --cc=crawley@dstc.edu.au \
    --cc=crawley@piglet.dstc.edu.au \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=suvarov454@users.sourceforge.net \
    /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).