public inbox for mauve-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Thomas Fitzsimmons <fitzsim@redhat.com>
Cc: Anthony Balkissoon <abalkiss@redhat.com>,
	 mauve-patches@sources.redhat.com
Subject: Re: RFC: add "not-a-test" tag to several tests
Date: Mon, 26 Jun 2006 16:49:00 -0000	[thread overview]
Message-ID: <1151340576.2557.3.camel@elsschot.wildebeest.org> (raw)
In-Reply-To: <44A00DF9.9040306@redhat.com>

On Mon, 2006-06-26 at 12:40 -0400, Thomas Fitzsimmons wrote:
> Mark Wielaard wrote:
> > They make it possible to use
> > RunnerProcess just as you could use SimpleTestHarness (e.g. echo
> > gnu.testlet.some.test | runtime RunnerProcess) by just returning when
> > stdin is empty (and in.readLine() returns null).
> 
> This can already be done using the current Harness:
> 
> jamvm Harness gnu.testlet.some.test
> 
> Harness also supports specifying multiple tests:
> 
> jamvm Harness gnu/testlet/java/awt/Frame/size1.java 
> gnu/testlet/javax/swing/JTable/addColumn.java

I know, but that is a terrible way for debugging. Hunting down a crasher
bug for example is really, really awkward using the Harness since it
does way too many things. When examining tests (especially under gdb)
for debugging you need to be able to run them just through the
RunnerProcess to make sure you are looking at just the thing that fails.
It works nicely with that one-liner patch though, so it isn't really
another way to run tests, it is just to make sure you can run the tests
by hand as if the Harness would run them.

Cheers,

Mark

  reply	other threads:[~2006-06-26 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 16:31 Anthony Balkissoon
2006-06-23 17:42 ` Tom Tromey
2006-06-26 14:20 ` Anthony Balkissoon
2006-06-26 14:40   ` Mark Wielaard
2006-06-26 16:40     ` Thomas Fitzsimmons
2006-06-26 16:49       ` Mark Wielaard [this message]
2006-06-27 16:05         ` Thomas Fitzsimmons
2006-06-27 16:38           ` Mark Wielaard

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=1151340576.2557.3.camel@elsschot.wildebeest.org \
    --to=mark@klomp.org \
    --cc=abalkiss@redhat.com \
    --cc=fitzsim@redhat.com \
    --cc=mauve-patches@sources.redhat.com \
    /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).