From: Cleber Rosa <crosa@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: philmd@redhat.com, jsnow@redhat.com, qemu-devel@nongnu.org,
Wainer dos Santos Moschetta <wainersm@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] tests/acceptance: Add boot linux with kvm test
Date: Sun, 30 Jun 2019 13:39:33 -0400 [thread overview]
Message-ID: <20190630173933.GB2820@localhost.localdomain> (raw)
In-Reply-To: <20190628201846.GK1862@habkost.net>
On Fri, Jun 28, 2019 at 05:18:46PM -0300, Eduardo Habkost wrote:
> On Fri, Jun 28, 2019 at 11:02:17AM -0400, Wainer dos Santos Moschetta wrote:
> > Until now the suite of acceptance tests doesn't exercise
> > QEMU with kvm enabled. So this introduces a simple test
> > that boots the Linux kernel and checks it boots on the
> > accelerator correctly.
> >
> > Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
>
> Why not just change the existing test_x86_64_pc() test case to
> use KVM by default? We can use "accel=kvm:tcg" to allow it to
> fall back to TCG if KVM is not available.
>
> --
> Eduardo
I though of something similar, but not exactly the same. An example
can be seen here:
https://travis-ci.org/clebergnu/qemu/jobs/551437429#L3350
IMO, it's a good practice to be able to briefly describe what a test
does, given its name. It's also very important for the test to
attempt to exercise the same behavior across executions.
I'm saying that because I don't think we should fallback to TCG if KVM
is not available, but instead, have two different tests that do each a
simpler and more predictable set of checks. This would make it
simpler to find KVM issues when a given test fails but the TCG
continues to pass. The tags (and other mechanisms) can be used to
select the tests that a given job should run though.
Regards!
- Cleber.
next prev parent reply other threads:[~2019-06-30 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 15:02 [Qemu-devel] [PATCH 0/3] Acceptance tests: boot Linux with KVM test Wainer dos Santos Moschetta
2019-06-28 15:02 ` [Qemu-devel] [PATCH 1/3] python/qemu: Allow to launch the VM without qmp Wainer dos Santos Moschetta
2019-06-28 15:02 ` [Qemu-devel] [PATCH 2/3] tests/acceptance: Introduce the "accel" tag Wainer dos Santos Moschetta
2019-06-28 15:02 ` [Qemu-devel] [PATCH 3/3] tests/acceptance: Add boot linux with kvm test Wainer dos Santos Moschetta
2019-06-28 20:18 ` Eduardo Habkost
2019-06-30 17:39 ` Cleber Rosa [this message]
2019-07-01 18:34 ` Eduardo Habkost
2019-07-01 20:29 ` Cleber Rosa
2019-07-05 15:43 ` Wainer dos Santos Moschetta
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=20190630173933.GB2820@localhost.localdomain \
--to=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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).