qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] .gitlab-ci.d/cirrus.yml: Shorten the runtime of the macOS and FreeBSD jobs
Date: Fri, 26 Jul 2024 17:59:38 +0100	[thread overview]
Message-ID: <ZqPV-s_7yav0eUT4@redhat.com> (raw)
In-Reply-To: <035f854c-78ff-4a8a-9356-1c55dca381b8@redhat.com>

On Fri, Jul 26, 2024 at 11:18:43AM +0200, Thomas Huth wrote:
> 
> Looks like the reduction of this patch was not enough, we've run out of
> Cirrus-CI compute time again ... does anybody have additional ideas how we
> could avoid that in the future?

QEMU keeps getting bigger, so our attempts to cut down on what we
build mean we keep testing a narrower & narrower subset of
functionality. We long ago culled the obvious wastage.

One thing is to optimize our code such that it is less expensive
for the compiler. I feel like we've done that periodically already
with refactoring header files. It is a complex problem with no
quick wins to reduce compile time. If someone knows of more low
hanging fruit though, speak up.

Cirrus CI supports a "bring your hardware" model. We could do
that for FreeBSD testing, by leveraging our existnig Azure
account further to provide VMs. If doing that though, it'd
be saner to just do it in GitLab context directly. This huas
the burn of *us* maintaining FreeBSD images,and updating
them every time a new FreeBSD is released. ie you can't just
stick on 12.0, because when 12.1 is released, the ports
packages get rebuilt against new 12.1 and frequently become
uninstallable on the older minor release. IOW, we would have
a continual burden in updating our images to track FreeBSD
minor releases. Also this doesn't solve our macOS needs since
you can't just run macOS in any VM, it has to be Apple HW.

Cirrus CI lets you buy more CI credits. IIUC we get 50 credits
free each month. I can't see QEMU's usage, since it is private
to admins only:

  https://cirrus-ci.com/settings/github/qemu

if it is anything like libvirt though, I'm going to expect that
most of our credits are consumed by macOS, not FreeBSD, since
Cirrus CI charges for macOS at a higher level.

To stop running out of credits I guess we'll want to buy an
extra 20 credits in each freeze period - ie 60 a year. They
charge $1 per credit.

Does the QEMU project have funds available to spend on things
like this ?  It unfortunately requires a credit card to buy
more credits, so somehow QEMU would have to re-imburse an
individual maintainer for the purchase.

Final option is to make contact with Cirrus CI owners, and
ask if they might wish to directly sponsor QEMU in terms of
granting us extra credits, in exchange for including them on
our sponsor's page https://www.qemu.org/sponsors/.


With 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:[~2024-07-26 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 10:01 [PATCH] .gitlab-ci.d/cirrus.yml: Shorten the runtime of the macOS and FreeBSD jobs Thomas Huth
2024-07-26  9:18 ` Thomas Huth
2024-07-26 16:59   ` 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=ZqPV-s_7yav0eUT4@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@redhat.com \
    --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 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).