qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
	qemu-devel@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Gustavo Romero" <gustavo.romero@linaro.org>,
	"Pierrick Bouvier" <pierrick.bouvier@linaro.org>
Subject: Re: [PATCH] tests/functional: add --debug CLI arg
Date: Thu, 17 Jul 2025 11:36:48 +0100	[thread overview]
Message-ID: <875xfrxfwf.fsf@draig.linaro.org> (raw)
In-Reply-To: <7924aab8-2d89-4b69-be5d-40ffb0c839a5@redhat.com> (Thomas Huth's message of "Thu, 17 Jul 2025 10:46:46 +0200")

Thomas Huth <thuth@redhat.com> writes:

> On 17/07/2025 10.42, Alex Bennée wrote:
>> Manos Pitsidianakis <manos.pitsidianakis@linaro.org> writes:
>> 
>>> Add argument parsing to functional tests to improve developer experience
>>> when running individual tests. All logs are printed to stdout
>>> interspersed with TAP output.
>>>
>>>    ./pyvenv/bin/python3 ../tests/functional/test_aarch64_virt.py --help
>>>    usage: test_aarch64_virt [-h] [-d]
>> Am I holding it wrong?
>>    ➜  ./pyvenv/bin/python
>> ../../tests/functional/test_aarch64_virt.py --help
>>    Traceback (most recent call last):
>>      File "/home/alex/lsrc/qemu.git/builds/all/../../tests/functional/test_aarch64_virt.py", line 16, in <module>
>>        from qemu_test import QemuSystemTest, Asset, exec_command_and_wait_for_pattern
>>      File "/home/alex/lsrc/qemu.git/tests/functional/qemu_test/__init__.py", line 14, in <module>
>>        from .testcase import QemuBaseTest, QemuUserTest, QemuSystemTest
>>      File "/home/alex/lsrc/qemu.git/tests/functional/qemu_test/testcase.py", line 26, in <module>
>>        from qemu.machine import QEMUMachine
>>    ModuleNotFoundError: No module named 'qemu'
>> I thought the point of the venv is we had all the modules we need
>> automatically available to the PYTHONPATH?
>
> The "qemu" module is special since we ship it in our repository. See
> the "PYTHONPATH" description in docs/devel/testing/functional.rst.

Is there anyway to setup the venv so it automatically does that?

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2025-07-17 10:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  6:08 [PATCH] tests/functional: add --debug CLI arg Manos Pitsidianakis
2025-07-16 16:23 ` Pierrick Bouvier
2025-07-17  8:42 ` Alex Bennée
2025-07-17  8:46   ` Thomas Huth
2025-07-17 10:36     ` Alex Bennée [this message]
2025-07-21  7:25       ` Thomas Huth
2025-07-17  8:47   ` Manos Pitsidianakis
2025-07-17 10:04     ` Alex Bennée
2025-07-17 10:13       ` Manos Pitsidianakis
2025-07-21 20:38   ` John Snow
2025-07-24 19:47     ` Thomas Huth
2025-08-07 21:46       ` John Snow
2025-09-09 10:37         ` Thomas Huth
2025-09-15 19:54           ` John Snow
2025-09-19  6:13             ` Thomas Huth
2025-07-17  9:21 ` Daniel P. Berrangé
2025-07-17  9:27   ` Manos Pitsidianakis
2025-07-17  9:39     ` Daniel P. Berrangé
2025-07-17 10:02       ` Manos Pitsidianakis

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=875xfrxfwf.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=gustavo.romero@linaro.org \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=philmd@linaro.org \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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).