From: Caio Carrara <ccarrara@redhat.com>
To: Cleber Rosa <crosa@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Laszlo Ersek" <lersek@redhat.com>, "Fam Zheng" <famz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 0/3] Bootstrap Python venv and acceptance/functional tests
Date: Wed, 17 Oct 2018 14:04:35 -0300 [thread overview]
Message-ID: <1c3df15f-c3d5-d638-cd33-fa05bfbbd516@redhat.com> (raw)
In-Reply-To: <20181017160539.12316-1-crosa@redhat.com>
On 17-10-2018 13:05, Cleber Rosa wrote:
> TL;DR
> =====
>
> Allow acceptance tests to be run with `make check-acceptance`.
>
> Details
> =======
>
> This introduces a Python virtual environment that will be setup within
> the QEMU build directory, that will contain the exact environment that
> tests may require.
>
> There's one current caveat: it requires Python 3, as it's based on the
> venv module. This was based on some discussions and perception about
> standardizing on Python 3, but can easily be made to accommodate Python
> 2 as well.
> (...)
Reviewed-by: Caio Carrara <ccarrara@redhat.com>
--
Caio Carrara
Software Engineer, Virt Team
Red Hat
ccarrara@redhat.com
prev parent reply other threads:[~2018-10-17 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 16:05 [Qemu-devel] [PATCH v6 0/3] Bootstrap Python venv and acceptance/functional tests Cleber Rosa
2018-10-17 16:05 ` [Qemu-devel] [PATCH v6 1/3] Bootstrap Python venv for tests Cleber Rosa
2018-10-17 19:30 ` Wainer dos Santos Moschetta
2018-10-17 16:05 ` [Qemu-devel] [PATCH v6 2/3] Acceptance tests: add make rule for running them Cleber Rosa
2018-10-17 16:05 ` [Qemu-devel] [PATCH v6 3/3] Travis support for the acceptance tests Cleber Rosa
2018-10-17 17:04 ` Caio Carrara [this message]
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=1c3df15f-c3d5-d638-cd33-fa05bfbbd516@redhat.com \
--to=ccarrara@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=lersek@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).