qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Ed Maste <emaste@freebsd.org>
Cc: "Fam Zheng" <fam@euphon.net>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] .cirrus.yml: basic compile and test for FreeBSD
Date: Tue, 22 Jan 2019 10:40:14 +0100	[thread overview]
Message-ID: <6272e5b7-477c-6a38-97cd-a16b94c209d5@redhat.com> (raw)
In-Reply-To: <CAPyFy2DNJvE4GbXxtzFJe8bPiXQm+bOmp+D_zVSCtaJML18vzw@mail.gmail.com>

On 2019-01-21 17:30, Ed Maste wrote:
> On Mon, 21 Jan 2019 at 10:16, Ed Maste <emaste@freebsd.org> wrote:
>>
>> To confirm, I have another build running now with
>> echo "Running with hw.ncpu=$(sysctl -n hw.ncpu)"
>> added.
> 
> Confirmed - https://cirrus-ci.com/build/5768962257190912:
> Running with hw.ncpu=8
> 
> If there is some sort of hanging test issue I could try wrapping it in
> timeout and outputting ps and other info upon failure.

Ok, I did some more tests today. First two runs were simply killed:

 https://cirrus-ci.com/build/5478092878381056
 https://cirrus-ci.com/build/5754149284085760

Then I tried to decrease the amount of resources to 4 CPUs and 8G of
RAM, but that timed out:

 https://cirrus-ci.com/build/6003268728651776

Then I finally increased the CPUs back to 8 again, but stick with 8G of
RAM, and that indeed finished in time successfully:

 https://cirrus-ci.com/build/6218565876187136

So yes, looks like 8 CPUs should work indeed, but I think you should
decrease the amount of memory of the VM, to make sure that it does not
get killed so easily. 8 GB of RAM should also be enough to compile QEMU,
as far as I can tell.

 Thomas


PS: I also removed the V=1 in my tests since otherwise the log was way
to verbose for my taste ... but that's likely really just a matter of taste.

  reply	other threads:[~2019-01-22  9:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 19:19 [Qemu-devel] [PATCH v2] .cirrus.yml: basic compile and test for FreeBSD Ed Maste
2019-01-17  6:28 ` Thomas Huth
2019-01-18 14:41   ` Ed Maste
2019-01-18 14:47 ` [Qemu-devel] [PATCH v3] " emaste
2019-01-21  9:13   ` Thomas Huth
2019-01-21 10:18     ` Thomas Huth
2019-01-21 15:16       ` Ed Maste
2019-01-21 16:30         ` Ed Maste
2019-01-22  9:40           ` Thomas Huth [this message]
2019-01-22 10:41             ` Peter Maydell
2019-01-22 13:42             ` Ed Maste
2019-01-22 14:09               ` Thomas Huth
2019-01-21 11:03   ` Alex Bennée
2019-01-21 15:20     ` Ed Maste
2019-01-21 15:36       ` Alex Bennée
2019-01-23 10:58 ` [Qemu-devel] [PATCH v2] " no-reply

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=6272e5b7-477c-6a38-97cd-a16b94c209d5@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=emaste@freebsd.org \
    --cc=fam@euphon.net \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).