From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Buildbot failure: MinGW
Date: Mon, 25 Nov 2013 08:00:13 +0100 [thread overview]
Message-ID: <1385362813.25009.6.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <5291D335.7040206@weilnetz.de>
On So, 2013-11-24 at 11:21 +0100, Stefan Weil wrote:
> Am 22.11.2013 13:51, schrieb Gerd Hoffmann:
> > Hi,
> >
> >>> 'make check' for MinGW cross builds needs an installation of wine to run
> >>> the resulting exe files.
> > I don't think it is a good idea to run tests for cross builds by
> > default.
> >
> > cheers,
> > Gerd
>
> Why not?
Because making them run requires extra setup effort on the host which
you can't assume is there.
> In this case (MinGW), setting up cross builds is rather easy,
> and also testing them with Wine seems to be easy and successful: it
> detects the current coroutine problem, for example.
It makes sense to be able to run those checks on wine, no question. But
simply assuming wine is there and run them unconditionally isn't a good
idea IMHO.
I think we should either have "make check" autodetect whenever wine is
present, or have a separate make target for tests which require wine
which is not run by default.
cheers,
Gerd
next prev parent reply other threads:[~2013-11-25 7:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJSP0QXtiYBE5xEgKwzy7hghT8=QPM_VfWdmMbWq1kJWJZC9LQ@mail.gmail.com>
2013-11-20 9:16 ` [Qemu-devel] Buildbot failure: qga/vss-win32/requester.h compile error Stefan Hajnoczi
2013-11-20 17:40 ` Tomoki Sekiyama
2013-11-20 17:49 ` Stefan Weil
2013-11-21 8:40 ` Stefan Hajnoczi
2013-11-22 6:56 ` [Qemu-devel] Buildbot failure: MinGW (was: qga/vss-win32/requester.h compile error) Stefan Weil
2013-11-22 10:54 ` Stefan Hajnoczi
2013-11-22 12:51 ` Gerd Hoffmann
2013-11-24 10:21 ` [Qemu-devel] Buildbot failure: MinGW Stefan Weil
2013-11-25 7:00 ` Gerd Hoffmann [this message]
2014-02-19 4:27 ` Stefan Weil
2014-02-19 10:05 ` Gerd Hoffmann
2014-02-19 11:53 ` Peter Maydell
2014-02-19 12:18 ` Thomas Huth
2014-02-19 13:07 ` Peter Maydell
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=1385362813.25009.6.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=sw@weilnetz.de \
/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 NNTP newsgroup(s).