From: Thomas Huth <thuth@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, berrange@redhat.com, sw@weilnetz.de
Subject: Re: [PATCH 0/3] Some win32 fixes
Date: Tue, 1 Oct 2019 16:11:30 +0200 [thread overview]
Message-ID: <981cb7af-2bcd-2c03-5bff-1e7a9215814d@redhat.com> (raw)
In-Reply-To: <20191001132609.23184-1-marcandre.lureau@redhat.com>
On 01/10/2019 15.26, Marc-André Lureau wrote:
> Hi,
>
> Here are a few patches that should fix some busy looping issues
> already reported >2y ago
> (https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg00420.html),
> and fixing test-char on win32.
>
> hmm, do we have any automated testing/CI on Windows (beside just
> cross-compilation)?
AFAIK we do not have any automated CI on Windows yet. But seems like
both, Travis and Cirrus, have Windows support, so you could add a test
to our .travis.yml or .cirrus.yml file, I think.
Thomas
prev parent reply other threads:[~2019-10-01 14:12 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é
2019-10-01 14:43 ` Stefan Weil
2019-10-01 14:03 ` Alex Bennée
2019-10-01 14:11 ` Thomas Huth [this message]
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=981cb7af-2bcd-2c03-5bff-1e7a9215814d@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--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).