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: Ed Maste <emaste@freebsd.org>,
	qemu-devel@nongnu.org, Li-Wen Hsu <lwhsu@freebsd.org>
Subject: Re: [PATCH] cirrus.yml: Split FreeBSD job into two parts
Date: Tue, 1 Sep 2020 09:57:11 +0100	[thread overview]
Message-ID: <20200901085711.GD345480@redhat.com> (raw)
In-Reply-To: <20200831154405.229706-1-thuth@redhat.com>

On Mon, Aug 31, 2020 at 05:44:05PM +0200, Thomas Huth wrote:
> The FreeBSD jobs currently hit the 1h time limit in the Cirrus-CI.
> We have to split the build targets here to make sure that the job
> finishes in time again. According to the Cirrus-CI docs and some
> tests that I did, it also seems like the total amount of CPUs that
> can be used for FreeBSD jobs is limited to 8, so each job now only
> gets 4 CPUs. That increases the compilation time of each job a little
> bit, but it still seems to be better to run two jobs with 4 CPUs each
> in parallel than to run two jobs with 8 CPUs sequentially.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  .cirrus.yml | 32 ++++++++++++++++++++++++++------
>  1 file changed, 26 insertions(+), 6 deletions(-)

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


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:[~2020-09-01  8:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 15:44 [PATCH] cirrus.yml: Split FreeBSD job into two parts Thomas Huth
2020-09-01  8:57 ` 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=20200901085711.GD345480@redhat.com \
    --to=berrange@redhat.com \
    --cc=emaste@freebsd.org \
    --cc=lwhsu@freebsd.org \
    --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 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).