public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Michael Koch <konqueror@gmx.de>
To: Norman Hendrich <hendrich@informatik.uni-hamburg.de>
Cc: classpath@gnu.org, mauve-discuss@sourceware.org
Subject: Re: classpath+mauve
Date: Fri, 14 Oct 2005 14:02:00 -0000	[thread overview]
Message-ID: <20051014140125.GC27035@asterix.konqueror.de> (raw)
In-Reply-To: <200510141356.j9EDuS4O015670@rzdspc1.informatik.uni-hamburg.de>

On Fri, Oct 14, 2005 at 03:56:28PM +0200, Norman Hendrich wrote:
> Hello David and Audrius,
> 
> first of all, thanks for your answers to my mauve-setup question(s).
> I tried the MakeTestClassList program, which seems to work fine.
> However, after spending another few hours trying to get the whole 
> testsuite running, my worst fears are confirmed... To summarize:
> 
> * writing new testcases is easy
> 
> * running individual testcases is easy (from the shell or eclipse)
> 
> * running parts of the testsuite via an index file works.
> 
> * BUT there is no easy way to run the whole testsuite. A developer
>   first has to create a custom list of exclusion testcases, before
>   running the remaining fraction of the testsuite... 

Not true. I just use the batch_run utility to run them all. I know that
Mark uses this too.


Cheers,
Michael
-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/

  reply	other threads:[~2005-10-14 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 13:56 classpath+mauve Norman Hendrich
2005-10-14 14:02 ` Michael Koch [this message]
2005-10-14 14:31   ` classpath+mauve Brian Jones

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=20051014140125.GC27035@asterix.konqueror.de \
    --to=konqueror@gmx.de \
    --cc=classpath@gnu.org \
    --cc=hendrich@informatik.uni-hamburg.de \
    --cc=mauve-discuss@sourceware.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).