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

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.

The patches are ok.  It's just that the whole concept of running
the harness in Linux and the tests in Wine is a little iffy,
since when a test times out, the Linux kill command makes
the Wine JVM unhappy.  Wine JVMs prefer to be killed by Windows kill commands.
- Dan

  parent reply	other threads:[~2007-08-28 15:10 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 [this message]
2007-08-28 18:04       ` Steve McKay☄
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=545d88bc0708280809w72d2d4ebl523bf4c2d1400d9d@mail.gmail.com \
    --to=dkegel@google.com \
    --cc=green@redhat.com \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=smckay@google.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).