From: Eduardo Habkost <ehabkost@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Cleber Rosa <crosa@redhat.com>, Fam Zheng <famz@redhat.com>,
Amador Pahim <amador@pahim.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] configure: Enable out-of-tree acceptance tests
Date: Wed, 6 Jun 2018 17:11:40 -0300 [thread overview]
Message-ID: <20180606201140.GZ7451@localhost.localdomain> (raw)
In-Reply-To: <2bdd428e-8790-7c1f-f324-4bc6b6923c15@amsat.org>
On Wed, Jun 06, 2018 at 04:36:16PM -0300, Philippe Mathieu-Daudé wrote:
> On 06/06/2018 04:24 PM, Eduardo Habkost wrote:
> > On Tue, Jun 05, 2018 at 11:45:03AM -0300, Philippe Mathieu-Daudé wrote:
> > [... something about config files ...]
> >>> And after that, the following would run all "console" tests:
> >>>
> >>> avocado run -t console
> >>>
> >>> How does this sound?
> >>
> >> For my use cases this doesn't worry me, I'll let Eduardo/Fam opine about
> >> use_test_dir_when_no_references_given.
> >
> > Well, I can't give an opinion because I couldn't understand
> > what's the final goal here.
>
> You cut too much, the relevant part is:
>
> On 05/30/2018 10:06 PM, Cleber Rosa wrote:
> > But at the same, there are security implications: `list` won't
> > load/execute any test code (different from, say, standard Python
> > unittests), while "run" obviously will. So "avocado run" may end up
> > running what users don't want if a malicious user controls
> > "$avocado_datadir_paths_test_dir".
The final goal still isn't clear to me. Why would somebody want
to use $avocado_datadir_paths_test_dir instead of just specifying
"." in the command-line?
>
> >
> > What exactly is missing in the current solution? Why
> > "avocado run -t console ." wouldn't work?
>
> It doesn't work in out-of-tree builds, I have to use the full path:
>
> >> build_dir$ avocado run
> /full/path/to/sources/qemu/tests/acceptance/boot_linux_console.py
Isn't the symlink you suggested a better solution than requiring
the user to edit a config file?
--
Eduardo
next prev parent reply other threads:[~2018-06-06 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 20:03 [Qemu-devel] [RFC PATCH] configure: Enable out-of-tree acceptance tests Philippe Mathieu-Daudé
2018-05-30 23:25 ` Eduardo Habkost
2018-05-31 1:06 ` Cleber Rosa
2018-06-05 14:45 ` Philippe Mathieu-Daudé
2018-06-06 19:24 ` Eduardo Habkost
2018-06-06 19:36 ` Philippe Mathieu-Daudé
2018-06-06 20:11 ` Eduardo Habkost [this message]
2018-06-06 20:23 ` Cleber Rosa
2018-06-06 23:19 ` Philippe Mathieu-Daudé
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=20180606201140.GZ7451@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=amador@pahim.org \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).