public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Roman Kennke <roman@kennke.org>
To: mauve-discuss@sources.redhat.com
Cc: classpath@gnu.org
Subject: Updating Mauve tags
Date: Sat, 14 Jan 2006 21:33:00 -0000	[thread overview]
Message-ID: <1137274393.7808.6.camel@localhost.localdomain> (raw)

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

Hi there,

(BTW: This is a Mauve topic, I CC the classpath list because the
mauve-discuss list seems so dead).

I see that we have a concept of tags in Mauve. That is a collection of
keys at the top of each test class. This way we can filter the tests.
ATM we have tags for the JDK versions like JDK1.4 JDK1.3 and so on and a
couple of other tags. However, it seems that they are not maintained in
a usable way, so most people simply include every tag that they can
think of (that is what's done in batch_run for example) to run all
tests.

I would like to fix the tagging of the tests with regard to the JDK
versions. And since the current reference is JDK1.5, I would naturally
start with this one. What I propose to do is run all the tests under
JDK1.5 and set the JDK1.5 tag for all tests that pass there. For all
tests that FAIL and have the JDK1.5 tag set, this tag would have to be
removed. Later I would like to do the same for JDK1.4 and JDK1.3. (I
have no JDK1.2 JDK1.1 or JDK1.0 available, otherwise I would probably do
the same for these).

What do you think about this? Maybe I completely misunderstand the
concept and working of the tags?

Cheers,
/Roman

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-01-14 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-14 21:33 Roman Kennke [this message]
2006-01-15 22:08 ` Mark Wielaard
2006-01-15 23:59   ` Roman Kennke
2006-01-16 10:25     ` Meskauskas Audrius
2006-01-16 10:32     ` Mark Wielaard
2006-01-16 10:59     ` David Gilbert

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=1137274393.7808.6.camel@localhost.localdomain \
    --to=roman@kennke.org \
    --cc=classpath@gnu.org \
    --cc=mauve-discuss@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).