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>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Ed Maste" <emaste@freebsd.org>,
	qemu-devel@nongnu.org, "Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: [PATCH] cirrus.yml: Exclude some targets in the FreeBSD job to speed up the build
Date: Fri, 28 Aug 2020 09:59:54 +0100	[thread overview]
Message-ID: <20200828085954.GE224144@redhat.com> (raw)
In-Reply-To: <20200824094410.6201-1-thuth@redhat.com>

On Mon, Aug 24, 2020 at 11:44:10AM +0200, Thomas Huth wrote:
> The FreeBSD jobs currently hit the 1h time limit in the Cirrus-CI.
> We've got to exclude some build targets here to make sure that the job
> finishes in time again. The targets that are excluded should not hurt
> much, since e.g. all the code from i386-softmmu is covered again by
> x86_64-softmmu.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  Not sure why the FreeBSD builds suddenly got slower and hit the 1h
>  time limit now. Looking at https://cirrus-ci.com/github/qemu/qemu
>  it seems like the FreeBSD jobs were already taking ca. 48 minutes
>  since quite a while, but since the Meson build system has been merged,
>  they now always hit the 1h limit. Could it be that Meson is slow on
>  FreeBSD?
>  
>  I hope disabling some of the "redundant" targets is ok for everybody
>  to get this working again. Alternatively, we could also introduce a
>  second FreeBSD job and run half of the targets in one job, and half
>  of the targets in the other job if that's preferred?

I'd probably suggest we go for two jobs, as there doesn't look like
any constraint on running multiple jobs that we'll hit any time
soon.


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 :|



  parent reply	other threads:[~2020-08-28  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24  9:44 [PATCH] cirrus.yml: Exclude some targets in the FreeBSD job to speed up the build Thomas Huth
2020-08-27 15:00 ` Daniel P. Berrangé
2020-08-28  4:28   ` Thomas Huth
2020-08-28  8:59 ` Daniel P. Berrangé [this message]
2020-08-28  9:54   ` Thomas Huth
2020-08-31  6:13     ` Thomas Huth

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=20200828085954.GE224144@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=emaste@freebsd.org \
    --cc=lwhsu@freebsd.org \
    --cc=pbonzini@redhat.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 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).