qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Cleber Rosa <crosa@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>, "Beraldo Leal" <bleal@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Fabien Chouteau" <chouteau@adacore.com>,
	"Willian Rampazzo" <willianr@redhat.com>,
	"KONRAD Frederic" <frederic.konrad@adacore.com>,
	qemu-ppc <qemu-ppc@nongnu.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Willian Rampazzo" <wrampazz@redhat.com>,
	"Hervé Poussineau" <hpoussin@reactos.org>,
	"Aleksandar Rikalo" <aleksandar.rikalo@rt-rk.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Aurelien Jarno" <aurelien@aurel32.net>,
	"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [PULL 3/6] Acceptance test: add "boot_linux" tests
Date: Tue, 24 Mar 2020 14:57:20 +0000	[thread overview]
Message-ID: <CAFEAcA9JQbMsQpm30nVb2XQWqV=TYE5nqEEzH4uznG_Rnarorw@mail.gmail.com> (raw)
In-Reply-To: <20200318001932.180617-4-crosa@redhat.com>

On Wed, 18 Mar 2020 at 00:19, Cleber Rosa <crosa@redhat.com> wrote:
>
> This acceptance test, validates that a full blown Linux guest can
> successfully boot in QEMU.  In this specific case, the guest chosen is
> Fedora version 31.
>
>  * x86_64, pc-i440fx and pc-q35 machine types, with TCG and KVM as
>    accelerators
>
>  * aarch64 and virt machine type, with TCG and KVM as accelerators
>
>  * ppc64 and pseries machine type with TCG as accelerator
>
>  * s390x and s390-ccw-virtio machine type with TCG as accelerator

I have noticed that these seem to slow down 'make check-acceptance'
a lot. At least for arm, the other tests run in check-acceptance take
perhaps 10 or 20 seconds a test. The
"tests/acceptance/boot_linux.py:BootLinuxAarch64.test_virt_tcg"
test takes about 240 seconds. Is it possible to make it faster ?

thanks
-- PMM


  reply	other threads:[~2020-03-24 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  0:19 [PULL 0/6] Python and tests (mostly acceptance) patches 2020-03-17 Cleber Rosa
2020-03-18  0:19 ` [PULL 1/6] python/qemu/qmp.py: QMP debug with VM label Cleber Rosa
2020-03-18  0:19 ` [PULL 2/6] Acceptance tests: introduce BUILD_DIR and SOURCE_DIR Cleber Rosa
2020-03-18  0:19 ` [PULL 3/6] Acceptance test: add "boot_linux" tests Cleber Rosa
2020-03-24 14:57   ` Peter Maydell [this message]
2020-03-18  0:19 ` [PULL 4/6] Acceptance tests: add make targets to download images Cleber Rosa
2020-03-18  0:19 ` [PULL 5/6] tests/docker: add CentOS 8 Dockerfile Cleber Rosa
2020-03-18  0:19 ` [PULL 6/6] tests/docker: make "buildah bud" output similar to "docker build" Cleber Rosa
2020-03-19 14:21 ` [PULL 0/6] Python and tests (mostly acceptance) patches 2020-03-17 Peter Maydell

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='CAFEAcA9JQbMsQpm30nVb2XQWqV=TYE5nqEEzH4uznG_Rnarorw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=aleksandar.rikalo@rt-rk.com \
    --cc=alex.bennee@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=bleal@redhat.com \
    --cc=chouteau@adacore.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=fam@euphon.net \
    --cc=frederic.konrad@adacore.com \
    --cc=hpoussin@reactos.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=wainersm@redhat.com \
    --cc=willianr@redhat.com \
    --cc=wrampazz@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).