All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Willian Rampazzo" <willianr@redhat.com>,
	"Yonggang Luo" <luoyonggang@gmail.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [RFC PATCH] gitlab-ci: Test compilation on Windows with MSYS2
Date: Fri, 9 Jul 2021 15:38:21 +0100	[thread overview]
Message-ID: <YOhfXcZRkyfO3zV5@redhat.com> (raw)
In-Reply-To: <c7f2d936-bc4c-4524-f152-6517c0345016@redhat.com>

On Fri, Jul 09, 2021 at 04:34:54PM +0200, Thomas Huth wrote:
> On 09/07/2021 10.20, Daniel P. Berrangé wrote:
> > On Fri, Jul 09, 2021 at 09:52:18AM +0200, Thomas Huth wrote:
> > > Gitlab also provides runners with Windows, we can use them to
> > > test compilation with MSYS2.
> > > 
> > > 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. And there is also still a problem with compiling
> > > the multiboot.bin in pc-bios/optionrom/, so this is currently
> > > disabled, too.
> > 
> > THe gitlab VM provisioning seems quite fast (2+1/2 minutes),
> > so I guess you mean the time is sunk in intsalling msys
> > packages.
> > 
> > In the crurent Cirrus job there's a bunch of code that is
> > done to cache all the msys install, so that 90% of the time
> > we're merely extracting a local zipfile.
> > 
> > I wonder if we can do similar caching here.
> 
> Maybe, yes. It might save 10 - 15 minutes or so, I guess.
> 
> > Perhaps even
> > have 2 seprate jobs running on the windows runner. The
> > first job can just build a zip file and store it as an
> > artifact and cache it in gitlab for speed. The second
> > job can do the actual build ?
> 
> I'm not sure ... the Windows builders are likely single-threaded on Gitlab,
> too, just like the Linux containers. So that the main problem - while we can
> compile with -j8 on Cirrus, it's 8 times slower on Gitlab.

Ah yes, good point.

Since we have cirrus integration for freebsd/macos now, we ought todo
the same for Windows too.  I auto-generated the freebsd/mac logic
with libvirt-ci, but I ignored msys since it was somewhat special
in its build commands. We can still set it up manually though to
integrate

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2021-07-09 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09  7:52 [RFC PATCH] gitlab-ci: Test compilation on Windows with MSYS2 Thomas Huth
2021-07-09  8:20 ` Daniel P. Berrangé
2021-07-09 14:34   ` Thomas Huth
2021-07-09 14:38     ` Daniel P. Berrangé [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=YOhfXcZRkyfO3zV5@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=luoyonggang@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=willianr@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.