From: Eric Blake <eblake@redhat.com>
To: Cleber Rosa <crosa@redhat.com>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <famz@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Philippe Mathieu-Daudé" <pmathieu@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Caio Carrara" <ccarrara@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v3 1/3] Bootstrap Python venv for tests
Date: Tue, 9 Oct 2018 13:06:22 -0500 [thread overview]
Message-ID: <8d5b4735-ccbd-dc8e-7f64-3f85ed58183c@redhat.com> (raw)
In-Reply-To: <20181009175740.13812-2-crosa@redhat.com>
On 10/9/18 12:57 PM, Cleber Rosa wrote:
> A number of QEMU tests are written in Python, and may benefit
> from an untainted Python venv.
>
> By using make rules, tests that depend on specific Python libs
> can set that rule as a requiment, along with rules that require
s/requiment/requirement/
> the presence or installation of specific libraries.
>
> The tests/venv-requirements.txt is supposed to contain the
> Python requirements that should be added to the venv created
> by check-venv.
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
> ---
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-10-09 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 17:57 [Qemu-devel] [PATCH v3 0/3] Bootstrap Python venv and acceptance/functional tests Cleber Rosa
2018-10-09 17:57 ` [Qemu-devel] [PATCH v3 1/3] Bootstrap Python venv for tests Cleber Rosa
2018-10-09 18:06 ` Eric Blake [this message]
2018-10-09 17:57 ` [Qemu-devel] [PATCH v3 2/3] Acceptance tests: add make rule for running them Cleber Rosa
2018-10-09 17:57 ` [Qemu-devel] [PATCH v3 3/3] Travis support for the acceptance tests Cleber Rosa
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=8d5b4735-ccbd-dc8e-7f64-3f85ed58183c@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=ccarrara@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=lersek@redhat.com \
--cc=pmathieu@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).