qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, alex.bennee@linaro.org, wrampazz@redhat.com,
	crosa@redhat.com, philmd@redhat.com, sgarzare@redhat.com
Subject: [PATCH 0/2] tests/acceptance: Add boot vmlinux test
Date: Fri,  6 Dec 2019 09:00:10 -0500	[thread overview]
Message-ID: <20191206140012.15517-1-wainersm@redhat.com> (raw)

This series add a new acceptance test: boot an uncompressed
Linux kernel built with CONFIG_PVH, so checking the PVH
capability introduced in QEMU 4.0 works.

The test implementation depends on [1] which is likely released
on next Avocado. So that will need a version 2 of this
series to bump Avocado version.

Also I want to use this as an example of a scenario that test
assets could be better managed. As you see on patch 01 the
kernel is built at test time on localhost. While Avocado provides
an API to easily fetch and build it, the whole process takes
reasonable time - besides the fact that localhost must have
all build dependencies installed. How could it be done better?

Nonetheless I argue in favor of merging this as is, and
gradually implement corrections to improve the tests assets
management. Also if eventually the test is proven to unacceptable
slow down the Travis CI then I can add a guard to skip it.

[1] https://github.com/avocado-framework/avocado/pull/3389

Wainer dos Santos Moschetta (2):
  tests/acceptance: Add PVH boot test
  .travis.yml: Add kernel build deps for acceptance tests

 .travis.yml             |  2 ++
 tests/acceptance/pvh.py | 48 +++++++++++++++++++++++++++++++++++++++++
 2 files changed, 50 insertions(+)
 create mode 100644 tests/acceptance/pvh.py

-- 
2.21.0



             reply	other threads:[~2019-12-06 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 14:00 Wainer dos Santos Moschetta [this message]
2019-12-06 14:00 ` [PATCH 1/2] tests/acceptance: Add PVH boot test Wainer dos Santos Moschetta
2019-12-06 15:04   ` Willian Rampazzo
2019-12-06 16:54   ` Cleber Rosa
2019-12-09 14:43     ` Wainer dos Santos Moschetta
2019-12-10  2:21       ` Cleber Rosa
2019-12-10 11:16   ` Philippe Mathieu-Daudé
2019-12-06 14:00 ` [PATCH 2/2] .travis.yml: Add kernel build deps for acceptance tests Wainer dos Santos Moschetta
2019-12-12 12:22   ` Alex Bennée
2019-12-06 16:42 ` [PATCH 0/2] tests/acceptance: Add boot vmlinux test Cleber Rosa
2019-12-10 11:05   ` Alex Bennée

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=20191206140012.15517-1-wainersm@redhat.com \
    --to=wainersm@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=fam@euphon.net \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@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).