public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: tromey@redhat.com
Cc: Dalibor Topic <robilad@kaffe.org>,
	Michael Koch <konqueror@gmx.de>,
	 Meskauskas Audrius <audriusa@bluewin.ch>,
	mauve-discuss@sources.redhat.com
Subject: Re: A place for the Classpath specific tests
Date: Tue, 15 Mar 2005 17:37:00 -0000	[thread overview]
Message-ID: <1110908210.1186.53.camel@localhost> (raw)
In-Reply-To: <m3d5u44qlz.fsf@localhost.localdomain>

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

Hi,

On Sat, 2005-03-12 at 12:21 -0700, Tom Tromey wrote:
> Dalibor> I'd say mauve, too. If a test is Classpath specific, then it
> Dalibor> can be tagged as such.
> 
> I agree.  We already put Classpath regression tests into Mauve.  For
> things that are truly Classpath-specific, say tests for gnu.*, we can
> just invent a new "classpath" tag and mention it in README.

OK. How about the following patch to the README:

--- README      4 Jan 2005 20:53:30 -0000       1.20
+++ README      15 Mar 2005 17:34:46 -0000
@@ -46,6 +46,15 @@
      JDK1.1  Run JDK1.1 tests only
      JDK1.2  Run JDK1.2 tests only

+     * The GNU_CLASSPATH tag selects and runs tests specific to the
+     (internal) core classes of the Free Software Foundation GNU Classpath
+     implementation (available from http://www.gnu.org/software/classpath)
+     on which a lot of free runtimes and compilers are build (but which are
+     not guaranteed to be available on all platforms).
+     These tests can be enable by adding GNU_CLASSPATH to your KEYS variable
+     and disabled by adding !GNU_CLASSPATH to the KEYS variable.
+     All such tests are in subdirectories under gnu/testlet/classpath.
+
 If an otherwise unrecognized tag QUUX is seen, and the file
 `mauve-QUUX' exists in the mauve source directory, then the contents
 of this file are treated as a list of tags.  For instance, here is the

By having a tag and a special subdirectory for these tests it should be
simple to enable/disable these special tests for the various ways people
run mauve (by hand, make, batch_run, ant script, etc).

Then we would need to move and retag the following files:

gnu/testlet/gnu/javax/swing/text/html/parser/support/Parser/ParserEntityResolverTest.java
gnu/testlet/gnu/javax/swing/text/html/parser/support/Parser/ParserTest.java
gnu/testlet/gnu/javax/swing/text/html/parser/support/Parser/parameterDefaulter_Test.java
gnu/testlet/gnu/javax/swing/text/html/parser/support/Parser/textPreProcessor_Test.java
gnu/testlet/gnu/javax/swing/text/html/parser/support/low/Buffer/Buffer_Test.javagnu/testlet/gnu/javax/swing/text/html/parser/support/low/Constants/Constants_Test.java
gnu/testlet/gnu/javax/swing/text/html/parser/support/low/ReaderTokenizer/ReaderTokenizer_Test.java

Did I miss any?
If people agree this is a good thing I will update the choose script and
batch_run to understand the new GNU_CLASSPATH tag.

Cheers,

Mark

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

  reply	other threads:[~2005-03-15 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 14:19 Meskauskas Audrius
2005-03-10 16:07 ` Michael Koch
2005-03-10 16:21   ` Dalibor Topic
2005-03-12 19:24     ` Tom Tromey
2005-03-15 17:37       ` Mark Wielaard [this message]
2005-03-15 17:55         ` Tom Tromey

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=1110908210.1186.53.camel@localhost \
    --to=mark@klomp.org \
    --cc=audriusa@bluewin.ch \
    --cc=konqueror@gmx.de \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=robilad@kaffe.org \
    --cc=tromey@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).