All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Gerd Hoffmann <kraxel@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Buildbot failure: MinGW
Date: Sun, 24 Nov 2013 11:21:41 +0100	[thread overview]
Message-ID: <5291D335.7040206@weilnetz.de> (raw)
In-Reply-To: <1385124694.3681.87.camel@nilsson.home.kraxel.org>

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? 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.

If we don't want tests for the MinGW cross build, the buildbot
configuration should to be changed - otherwise we'll always see "failed
test" instead of "build successful" for MinGW.

Cheers,
Stefan

  reply	other threads:[~2013-11-24 10:22 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             ` Stefan Weil [this message]
2013-11-25  7:00               ` [Qemu-devel] Buildbot failure: MinGW Gerd Hoffmann
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=5291D335.7040206@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.