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.. (batch_run and runner script documentation)
Date: Fri, 16 Apr 2004 12:01:00 -0000 [thread overview]
Message-ID: <1082116861.1971.13.camel@elsschot.wildebeest.org> (raw)
In-Reply-To: <1082114942.1971.9.camel@elsschot.wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
Hi,
On Fri, 2004-04-16 at 13:29, Mark Wielaard wrote:
> On Fri, 2004-04-16 at 11:30, Andrew Haley wrote:
> > Mark Wielaard writes:
> > > Is it documented?
> >
> > Yeah, right.
>
> :)
> I admit to be guilty of not documenting my batch_run and runner script.
> But a little blurb in the README wouldn't hurt.
> If I promise to add something about my scripts, could you add something
> about yours? At least how to invoke the thing...
OK. I added the following to 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 --]
next prev parent reply other threads:[~2004-04-16 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 13:05 Some issues 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 ` Mark Wielaard [this message]
2004-04-16 12:04 ` Andrew Haley
2004-04-22 21:41 ` Mark Wielaard
2004-04-15 22:14 ` Mark Wielaard
2004-05-07 11:54 ` John Leuner
2004-05-07 13:25 ` Thomas
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=1082116861.1971.13.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).