public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Steve McKay☄" <smckay@google.com>
To: "Anthony Green" <green@redhat.com>
Cc: "Daniel Kegel" <dkegel@google.com>, mauve-discuss@sources.redhat.com
Subject: Re: Patches for running mauve against wine + win32 vm
Date: Tue, 28 Aug 2007 18:04:00 -0000	[thread overview]
Message-ID: <4f2ee4520708281103i1e47780i68b28f4b0ee6728f@mail.gmail.com> (raw)
In-Reply-To: <46D42F38.8030100@redhat.com>

Hi Anthony,

I experienced a problem unrelated to these changes, in which some
tests were not timing out correctly causing the entire suite to hang.
As you noted, that problem isn't addressed in the patch. Dan made
mention of that due to the fact that one of the changes in the patch
("Transform path to class name prior to passing to RunnerProcess") was
needed in order to get thing working with the mixed Linux/Wine
environment. The change is still reasonable and I'd still like to see
the full patch applied.

Changes (from the changelog patch):

+	* Harness.java (runTest):
+	Transform path to class name prior to passing to RunnerProcess.
+    * Harness.java (processFolder):
+	Don't try to compile "Uses:" resources when auto compilation is
+	disabled.
+    * Harness.java (setupHarness):
+	Update flags processing for "-compile" flag to require an argument.
+	Correct erroneous error message.

On 8/28/07, Anthony Green <green@redhat.com> wrote:
> Daniel Kegel wrote:
> > It turns out this might not be such a good idea after all
> > for those tests which time out,
>
> Are you saying that you not want these patches applied?  I don't see
> anything in here related to timeouts.
>
> Thanks,
>
> AG
>
> > since Wine JVMs object if you kill them with a unix kill command.
> > Steve tried running everything in Wine, and the timeout kill
> > works more smoothly.
> >
> >
> > On 8/27/07, Steve McKay☄ <smckay@google.com> wrote:
> >> Hi All,
> >>
> >> I mailed this patch to mauve-patches more than three weeks back. I
> >> haven't received any response. Is that list dead?
> >>
> >> How should I go about getting patches applied?
> >>
> >> ---------- Forwarded message ----------
> >> From: Steve McKay☄ <smckay@google.com>
> >> Date: Aug 3, 2007 2:09 PM
> >> Subject: Patches for running mauve against wine + win32 vm
> >> To: mauve-patches@sourceware.org
> >> Cc: Dan Kegel <dkegel@google.com>
> >>
> >>
> >> Hi All,
> >>
> >> I've been working on running the mauve test suite against a wine
> >> hosted jvm. This is primarily to check the behavior of wine + an
> >> embedded win32 jvm. I have a couple small patches resulting from my
> >> work (attached). How do I go about getting them reviewed/applied?
> >>
> >> --
> >> Steve McKay <smckay@google.com>
> >>
> >>
> >>
> >> --
> >> Steve McKay <smckay@google.com>
> >>
> >>
>
>
>


-- 
Steve McKay <smckay@google.com>

  parent reply	other threads:[~2007-08-28 18:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4f2ee4520708031409o723d606bx78689a245f9fb5ef@mail.gmail.com>
2007-08-27 20:01 ` Fwd: " Steve McKay☄
2007-08-28  0:40   ` Daniel Kegel
     [not found]     ` <46D42F38.8030100@redhat.com>
2007-08-28 15:10       ` Daniel Kegel
2007-08-28 18:04       ` Steve McKay☄ [this message]
2007-08-31 17:33         ` Steve McKay☄
2007-09-06 21:07           ` Steve McKay☄
2007-09-06 21:39             ` Daniel Kegel
2007-09-07  5:16               ` Casey Marshall
2007-09-07 22:50                 ` Steve McKay☄
     [not found]                   ` <46E1DCB1.8090405@redhat.com>
2007-09-12 22:32                     ` Steve McKay☄

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=4f2ee4520708281103i1e47780i68b28f4b0ee6728f@mail.gmail.com \
    --to=smckay@google.com \
    --cc=dkegel@google.com \
    --cc=green@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).