public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: mauve-discuss@sources.redhat.com
Subject: Re: Disabled tests
Date: Tue, 29 Nov 2005 15:58:00 -0000	[thread overview]
Message-ID: <20051129155837.GD5325@redhat.com> (raw)
In-Reply-To: <1133273779.6994.216.camel@localhost.localdomain>

Mark Wielaard wrote:
> On Tue, 2005-11-29 at 13:51 +0000, Gary Benson wrote:
> > What do we do with failing tests?
> 
> I think we should have xfail files for them.  But currently we don't
> really have up to date ones.  And in the past various runtimes had
> completely different failure behavior making it unclear what the
> "correct" xfail file would be.
> 
> I hope the work of Edwin from teh Cacao team will help here since
> the produce lists of common failures between runtimes.
> 
> > The reason I ask is that I just noticed that the listRoots test in
> > gnu/testlet/java/io/File/security.java has been disabled in a
> > totally non-obvious way.  Should I reenable it?
>
> I think so. I have worked on this, but it is so obscure that I
> cannot really see the how and what should be happening here. Sorry
> about that.

In this case there's nothing saying why it's disabled.  The initial
revision (1.1, July 2003) had the test: it was commented out in the
next commit (1.2, March 2004) which was a total rewrite of the whole
file.  I don't think the test ever passed in Classpath, so it's
possible the guy disabled it while he was rewriting and then forgot to
reenable it before the commit.

The javadoc here makes is pretty clear what needs checking.
Does anyone mind if I reenable it?

Cheers,
Gary

  reply	other threads:[~2005-11-29 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29 13:52 Gary Benson
2005-11-29 14:16 ` Mark Wielaard
2005-11-29 15:58   ` Gary Benson [this message]
2005-11-29 21:48     ` 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=20051129155837.GD5325@redhat.com \
    --to=gbenson@redhat.com \
    --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).