From: Brian Jones <cbj@nc.rr.com>
To: Michael Koch <konqueror@gmx.de>
Cc: Norman Hendrich <hendrich@informatik.uni-hamburg.de>,
classpath@gnu.org, mauve-discuss@sourceware.org
Subject: Re: classpath+mauve
Date: Fri, 14 Oct 2005 14:31:00 -0000 [thread overview]
Message-ID: <434FC129.3030603@nc.rr.com> (raw)
In-Reply-To: <20051014140125.GC27035@asterix.konqueror.de>
Michael Koch wrote:
>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
>
>
Yes, due to the nature of how a JVM can fail... especially with respect
to hanging and doing nothing, you have to wrap execution of each test
case in a fashion that will kill the JVM if it does not exit in a
reasonable period of time. I think this batch_run utility does that. I
used to have a nice little set of scripts that did something similar and
created pretty graphs.
prev parent reply other threads:[~2005-10-14 14:31 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 ` classpath+mauve Michael Koch
2005-10-14 14:31 ` Brian Jones [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=434FC129.3030603@nc.rr.com \
--to=cbj@nc.rr.com \
--cc=classpath@gnu.org \
--cc=hendrich@informatik.uni-hamburg.de \
--cc=konqueror@gmx.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).