From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Nelson Chen <nelson@mindflakes.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Stefan Weil" <sw@weilnetz.de>
Subject: Re: [PATCH 0/3] Some win32 fixes
Date: Tue, 1 Oct 2019 15:54:46 +0200 [thread overview]
Message-ID: <58330557-6f23-1477-c603-3ef758d66a60@redhat.com> (raw)
In-Reply-To: <CAFEAcA8SZnh7iyf5ebChJ=Seu+u7thuhzmLayoYnpa69u+_K-Q@mail.gmail.com>
On 10/1/19 3:44 PM, Peter Maydell wrote:
> On Tue, 1 Oct 2019 at 14:43, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> On 01/10/19 15:26, Marc-André Lureau wrote:
>>> hmm, do we have any automated testing/CI on Windows (beside just
>>> cross-compilation)?
>>
>> Nope. :(
>
> I did wonder whether it would be possible to get 'make check'
> passing under Wine, but never investigated...
Nelson Chen started to use Azure CI:
https://github.com/nelsonjchen/nc-qemu/blob/master/.azure/msys2-build.sh
He posted some notes here:
https://mindflakes.com/projects/nc-qemu/
I have this link in my CI TODO to try to upstream it and run 'make
check' but it is not a high priority.
next prev parent reply other threads:[~2019-10-01 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 13:26 [PATCH 0/3] Some win32 fixes Marc-André Lureau
2019-10-01 13:26 ` [PATCH 1/3] util: WSAEWOULDBLOCK on connect should map to EINPROGRESS Marc-André Lureau
2019-10-01 13:56 ` Philippe Mathieu-Daudé
2019-10-01 13:26 ` [PATCH 2/3] tests: skip serial test on windows Marc-André Lureau
2019-10-01 13:48 ` Philippe Mathieu-Daudé
2019-10-01 13:26 ` [PATCH 3/3] win32: fix main-loop busy loop on socket/fd event Marc-André Lureau
2019-10-01 21:20 ` James Le Cuirot
2019-10-01 13:39 ` [PATCH 0/3] Some win32 fixes Paolo Bonzini
2019-10-01 13:44 ` Peter Maydell
2019-10-01 13:54 ` Philippe Mathieu-Daudé [this message]
2019-10-01 14:43 ` Stefan Weil
2019-10-01 14:03 ` Alex Bennée
2019-10-01 14:11 ` Thomas Huth
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=58330557-6f23-1477-c603-3ef758d66a60@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=nelson@mindflakes.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).