public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Balkissoon <abalkiss@redhat.com>
To: Edwin Steiner <edwin.steiner@gmx.net>
Cc: mauve-discuss@sourceware.org
Subject: Re: Problem with auto compilation and 	gnu.testlet.java.security.Engine.getInstance
Date: Thu, 10 Aug 2006 15:52:00 -0000	[thread overview]
Message-ID: <1155225137.14423.81.camel@tony.toronto.redhat.com> (raw)
In-Reply-To: <20060810122151.GA22953@localhost.localdomain>

On Thu, 2006-08-10 at 14:21 +0200, Edwin Steiner wrote:
> Hi!
> 
> When testing cacao with mauve we had a FAIL that only occurred on the
> first test run in a clean mauve checkout.
> 
> The reason is that when running the testlet
> 
>     gnu.testlet.java.security.Engine.getInstance
> 
> mauve auto compilation misses the required class
> 
>     gnu.testlet.java.security.MessageDigest.MauveDigest
> 
> This class is later compiled when the MessageDigest testlet is run,
> so the FAIL is not reproducible later.
> 
> Any idea what to do about this?
> 
> Cheers,
> -Edwin
> 

So the test compiles and runs, but fails because it requires MauveDigest
and can't find it?  I've tried running the test after a clean checkout,
and it works, but there are some failures.  So I'm guessing it falls
back to some default behaviour when it can't find MauveDigest?

I see that the test file has the "// Uses:" note, I guess we have to
make Mauve search for that and autocompile the needed files.

Tony

  reply	other threads:[~2006-08-10 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10 12:21 Edwin Steiner
2006-08-10 15:52 ` Anthony Balkissoon [this message]
2006-08-10 21:02   ` Edwin Steiner

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=1155225137.14423.81.camel@tony.toronto.redhat.com \
    --to=abalkiss@redhat.com \
    --cc=edwin.steiner@gmx.net \
    --cc=mauve-discuss@sourceware.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).