All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Yonggang Luo" <luoyonggang@gmail.com>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>,
	"Thomas Huth" <thuth@redhat.com>, QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH] gitlab-ci: Test compilation on Windows with MSYS2
Date: Wed, 17 Nov 2021 13:52:57 +0000	[thread overview]
Message-ID: <874k8ax504.fsf@linaro.org> (raw)
In-Reply-To: <623c1883-4ac9-e615-7a58-b0d781e19aeb@amsat.org>


Philippe Mathieu-Daudé <f4bug@amsat.org> writes:

> On 11/16/21 08:05, Marc-André Lureau wrote:
>> Hi
>> 
>> On Mon, Nov 15, 2021 at 6:31 PM Philippe Mathieu-Daudé <f4bug@amsat.org
>> <mailto:f4bug@amsat.org>> wrote:
>> 
>>     On 11/15/21 15:06, Thomas Huth wrote:
>>     > Gitlab also provides runners with Windows, we can use them to
>>     > test compilation with MSYS2, in both, 64-bit and 32-bit.
>>     >
>>     > However, it takes quite a long time to set up the VM, so to
>>     > stay in the 1h time frame, we can only compile and check one
>>     > target here.
>> 
>> 
>> I wonder why gitlab does not offer the docker executor. On the
>> freedesktop gitlab instance, they have windows docker executor, which
>> speeds up the build time. Maybe we could also have our own Windows
>> runner for qemu?
>
> We could, foss.org provides the QEMU project with x86 VMs resources
> we are not using. What we miss is a sysadmin willing to setup &
> maintain a such runner.

I think we might also have Azure credits from MS, but the same issues
about admin and setup probably exist.

-- 
Alex Bennée


  reply	other threads:[~2021-11-17 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 14:06 [PATCH] gitlab-ci: Test compilation on Windows with MSYS2 Thomas Huth
2021-11-15 14:29 ` Philippe Mathieu-Daudé
2021-11-16  7:05   ` Marc-André Lureau
2021-11-16  8:26     ` Philippe Mathieu-Daudé
2021-11-17 13:52       ` Alex Bennée [this message]
2021-11-17 14:44         ` Daniel P. Berrangé

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=874k8ax504.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=luoyonggang@gmail.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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.